From: Tony Breeds <tony@bakeyournoodle•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: LinuxPPC-dev <linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH] powerpc: 44x: Add mtd ndfc to the ppx44x defconfig
Date: Wed, 23 Nov 2011 14:21:57 +1100 [thread overview]
Message-ID: <20111123032155.GC25264@thor.bakeyournoodle.com> (raw)
In-Reply-To: <1322012084.14573.19.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
On Wed, Nov 23, 2011 at 12:34:44PM +1100, Benjamin Herrenschmidt wrote:
> On Tue, 2011-11-22 at 20:04 -0500, Josh Boyer wrote:
> > On Tue, Nov 22, 2011 at 6:50 PM, Tony Breeds <tony@bakeyournoodle•com> wrote:
> > > Signed-off-by: Tony Breeds <tony@bakeyournoodle•com>
> >
> > Acked-by: Josh Boyer <jwboyer@gmail•com>
> >
> > Ben, I don't have anything particularly urgent for 3.2 and this seems
> > like it is well within the 3.2 window (defconfig updates usually come
> > later). Want to pick this up yourself, or do you want me to prep a
> > tree somewhere?
>
> I'm working on 3.3 right now, so I'd rather you throw this in there, I
> doesn't seem to be particularily urgent for 3.2 is it? (who actually
> uses 4xx_defconfig ?)
It's mostly for linux-next / kisskb
There was a compiler error added to ndfc in upstream[1]. The change was in
linux-next but nothing currently builds that code. If we update
4xx_defconfig then linux-next will catch errors sooner.
So it's not urgent, but it doesn't hurt
[1] http://patchwork.ozlabs.org/patch/127000/
Yours Tony
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-23 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 23:50 [PATCH] powerpc: 44x: Add mtd ndfc to the ppx44x defconfig Tony Breeds
2011-11-23 1:04 ` Josh Boyer
2011-11-23 1:34 ` Benjamin Herrenschmidt
2011-11-23 3:21 ` Tony Breeds [this message]
2011-11-23 3:22 ` Josh Boyer
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=20111123032155.GC25264@thor.bakeyournoodle.com \
--to=tony@bakeyournoodle$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox