From: Josh Boyer <jwboyer@gmail.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: Tue, 22 Nov 2011 22:22:16 -0500 [thread overview]
Message-ID: <CA+5PVA4HqcCca15urmfUaQCBC4tKmEbgNJAJViXZh9QXw2s3DQ@mail.gmail.com> (raw)
In-Reply-To: <1322012084.14573.19.camel@pasglop>
On Tue, Nov 22, 2011 at 8:34 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> 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> w=
rote:
>> > 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). =A0Want 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
Urgent, no. I'll get a tree going after the holidays.
> uses 4xx_defconfig ?)
The linux-next tree builds it. It would have caught a compile error
in the NDFC driver much earlier if we had it enabled in the defconfig.
josh
prev parent reply other threads:[~2011-11-23 3:22 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
2011-11-23 3:22 ` Josh Boyer [this message]
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=CA+5PVA4HqcCca15urmfUaQCBC4tKmEbgNJAJViXZh9QXw2s3DQ@mail.gmail.com \
--to=jwboyer@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).