From: "Wu, Bryan" <bryan.wu@analog.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: "Wu, Bryan" <bryan.wu@analog.com>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
bert hubert <bert.hubert@netherlabs.nl>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm try#2] Blackfin: architecture update patch
Date: Fri, 23 Mar 2007 14:31:13 +0800 [thread overview]
Message-ID: <1174631473.18866.24.camel@roc-desktop> (raw)
In-Reply-To: <20070323061232.GA27616@linux-sh.org>
On Fri, 2007-03-23 at 15:12 +0900, Paul Mundt wrote:
> On Fri, Mar 23, 2007 at 02:04:30PM +0800, Wu, Bryan wrote:
> > This is the latest blackfin update patch. Because there are lots of
> > issue fixing in this one, I put all modification in one update patch
> > which is located in:
> > https://blackfin.uclinux.org/gf/download/frsrelease/39/2707/blackfin-arch-2.6.21-rc4-mm1-update.patch
> >
> I hope these will split up logically in the future so it's possible to
> reply to them without having to do manual mangling..
>
>From now on, I will follow this rule. Thanks
> The patch generally looks fine, this is the only thing that really jumped
> out:
>
> > Index: linux-2.6/include/asm-blackfin/pgtable.h
> > ===================================================================
> > --- linux-2.6.orig/include/asm-blackfin/pgtable.h
> > +++ linux-2.6/include/asm-blackfin/pgtable.h
> > @@ -59,4 +59,12 @@
> > #define VMALLOC_START 0
> > #define VMALLOC_END 0xffffffff
> >
> > +#define __HAVE_ARCH_ENTER_LAZY_CPU_MODE
> > +#define arch_enter_lazy_cpu_mode() do {} while (0)
> > +#define arch_leave_lazy_cpu_mode() do {} while (0)
> > +
> > +#define __HAVE_ARCH_ENTER_LAZY_MMU_MODE
> > +#define arch_enter_lazy_mmu_mode() do {} while (0)
> > +#define arch_leave_lazy_mmu_mode() do {} while (0)
> > +
> > #endif /* _BLACKFIN_PGTABLE_H */
>
> asm-generic/pgtable.h already does this if you don't explicitly define
> __HAVE_ARCH_ENTER_LAZY_{CPU,MMU}_MODE. So please kill this entirely. If
> you forgot to include asm-generic/pgtable.h, that's another matter..
OK, I will check with this. Adding this dummy function is because
compiling will fail.
Best Regards,
-Bryan Wu
next prev parent reply other threads:[~2007-03-23 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1174471618.5648.50.camel@roc-desktop>
2007-03-21 10:25 ` [PATCH -mm 1/4] Blackfin: architecture update patch Arnd Bergmann
2007-03-21 10:33 ` Wu, Bryan
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 [this message]
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
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=1174631473.18866.24.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 \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.