netdev - Re: [PATCH 10/10] pxa: make littleton to use the new smc91x platform data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Jun 2008 14:18:00 +0800
From:	Eric Miao <eric.y.miao@...il.com>
To:	Jeff Garzik <jeff@...zik.org>
CC:	linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>,
	linux-netdev <netdev@...r.kernel.org>,
	Nicolas Pitre <nico@....org>,
	Magnus Damm <magnus.damm@...il.com>,
	Eric Miao <eric.miao@...vell.com>
Subject: Re: [PATCH 10/10] pxa: make littleton to use the new smc91x platform
 data

Jeff Garzik wrote:
> Eric Miao wrote:
>> From: Eric Miao <eric.miao@...vell.com>
>>
>> Signed-off-by: Eric Miao <eric.miao@...vell.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.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html