From: Eric Miao <eric.y.miao@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
linux-netdev <netdev@vger.kernel.org>,
Nicolas Pitre <nico@cam.org>, Magnus Damm <magnus.damm@gmail.com>,
Eric Miao <eric.miao@marvell.com>
Subject: Re: [PATCH 10/10] pxa: make littleton to use the new smc91x platform data
Date: Fri, 27 Jun 2008 14:18:00 +0800 [thread overview]
Message-ID: <48648618.5060900@gmail.com> (raw)
In-Reply-To: <4864816F.5070407@garzik.org>
Jeff Garzik wrote:
> Eric Miao wrote:
>> From: Eric Miao <eric.miao@marvell.com>
>>
>> Signed-off-by: Eric Miao <eric.miao@marvell.com>
>> ---
>> arch/arm/mach-pxa/littleton.c | 9 +++++++++
>> drivers/net/smc91x.h | 3 ++-
>> 2 files changed, 11 insertions(+), 1 deletions(-)
>
> The rest of the patches seem OK.
>
> What do ARM people prefer -- should I ACK this series, and let it be
> merged via an ARM tree?
>
Well, I guess there are still some smc91x patches around and I'm not
sure if they will go inside the next merge window. So ideally, it'll
be best for "smc91x: *" patches go through the net-2.6, and I can
manage the rest to go through Russell's tree.
If you are OK with this, I'll send the smc91x specific patches to
you, together with Nico's Ack and a minor modification suggestion.
And either way will work if you prefer this to go through Russell's
arm tree.
> The series is mainly platform-oriented rather than net-oriented.
>
>
Yes, indeed.
next prev parent reply other threads:[~2008-06-27 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 9:47 [PATCH 10/10] pxa: make littleton to use the new smc91x platform data Eric Miao
2008-06-27 0:04 ` Nicolas Pitre
2008-06-27 5:58 ` Jeff Garzik
2008-06-27 6:18 ` Eric Miao [this message]
2008-06-30 12:24 ` Russell King - ARM Linux
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=48648618.5060900@gmail.com \
--to=eric.y.miao@gmail.com \
--cc=eric.miao@marvell.com \
--cc=jeff@garzik.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nico@cam.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.