LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Wu, Bryan" <bryan.wu@analog.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: bryan.wu@analog.com, Andrew Morton <akpm@linux-foundation.org>,
Paul Mundt <lethal@linux-sh.org>,
bert hubert <bert.hubert@netherlabs.nl>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 1/4] Blackfin: architecture update patch
Date: Wed, 21 Mar 2007 18:33:19 +0800 [thread overview]
Message-ID: <1174473199.5648.62.camel@roc-desktop> (raw)
In-Reply-To: <200703211125.39816.arnd@arndb.de>
On Wed, 2007-03-21 at 11:25 +0100, Arnd Bergmann wrote:
> On Wednesday 21 March 2007, Wu, Bryan wrote:
>
> > @@ -97,6 +97,11 @@ static inline void leds_switch(int flag)
> > /*
> > * The idle loop on BFIN
> > */
> > +#ifdef CONFIG_IDLE_L1
> > +static inline void default_idle(void)__attribute__((l1_text));
> > +void cpu_idle(void)__attribute__((l1_text));
> > +#endif
> > +
>
> A forward declaration for an inline function seems rather pointless.
> Moreover, marking default_idle both l1_text and inline seems
> contradicting, right?
>
> > diff -purN linux-2.6-orig/include/asm-blackfin/asm-offsets.h linux-2.6/include/asm-blackfin/asm-offsets.h
> > --- linux-2.6-orig/include/asm-blackfin/asm-offsets.h 1970-01-01 08:00:00.000000000 +0800
> > +++ linux-2.6/include/asm-blackfin/asm-offsets.h 2007-03-21 15:21:10.000000000 +0800
> > @@ -0,0 +1,89 @@
> > +#ifndef __ASM_OFFSETS_H__
> > +#define __ASM_OFFSETS_H__
> > +/*
> > + * DO NOT MODIFY.
> > + *
> > + * This file was generated by Kbuild
>
> This file should be in the exclude list for your diff, it is generally not
> shipped with the kernel sources.
Got, I will fix it.
>
> > +#ifndef __ASSEMBLY__
> > +
> > +static inline unsigned char readb(volatile unsigned char *addr)
> > +{
>
> The prototype for this should normally contain an __iomem.
> This kind of error is normally caught by running 'make C=1'
> to use the 'sparse' tool. If you have not run that yet,
> you should start to, as it finds a number of common bugs.
>
> > +/*
> > + * Map some physical address range into the kernel address space.
> > + */
> > +static inline void *__ioremap(unsigned long physaddr, unsigned long size,
> > + int cacheflag)
> > +{
> > + return (void *)physaddr;
> > +}
>
> Likewise, this should return an __iomem pointer.
It will be fixed as soon as possible.
>
> The rest of the patch looks good to me.
>
> Arnd <><
I sent 4 mail to LKML, but this one lost. Arnd, can you receive this
email from LKML.
Thanks a lot
-Bryan Wu
next prev parent reply other threads:[~2007-03-21 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1174471618.5648.50.camel@roc-desktop>
2007-03-21 10:25 ` Arnd Bergmann
2007-03-21 10:33 ` Wu, Bryan [this message]
2007-03-21 10:38 ` Arnd Bergmann
2007-03-21 12:56 ` Paul Mundt
2007-03-21 15:39 ` Mike Frysinger
2007-03-23 6:04 ` [PATCH -mm try#2] " Wu, Bryan
2007-03-23 6:12 ` Paul Mundt
2007-03-23 6:31 ` Wu, Bryan
2007-03-23 7:59 ` Andrew Morton
2007-03-23 8:14 ` Wu, Bryan
2007-03-21 13:06 ` [PATCH -mm 1/4] " Arnd Bergmann
[not found] <1174472363.5648.58.camel@roc-desktop>
2007-03-21 22:53 ` Andrew Morton
2007-03-22 2:24 ` Wu, Bryan
2007-03-22 4:08 ` Andrew Morton
2007-03-22 5:47 ` Wu, Bryan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1174473199.5648.62.camel@roc-desktop \
--to=bryan.wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bert.hubert@netherlabs.nl \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH -mm 1/4] Blackfin: architecture update patch' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).