netdev - Re: [PATCH REPOST 0/5] convert arm platforms to smsc911x

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]

Message-Id: <1232352274.23192.25.camel@localhost>
Date:	Mon, 19 Jan 2009 16:04:34 +0800
From:	"stanley.miao" <stanley.miao@...driver.com>
To:	David Miller <davem@...emloft.net>
Cc:	steve.glendinning@...c.com,
	linux-arm-kernel@...ts.arm.linux.org.uk, netdev@...r.kernel.org,
	linux@....linux.org.uk, ian.saturley@...c.com
Subject: Re: [PATCH REPOST 0/5] convert arm platforms to smsc911x

On Sun, 2009-01-18 at 21:53 -0800, David Miller wrote:
> From: Steve Glendinning <steve.glendinning@...c.com>
> Date: Thu, 15 Jan 2009 09:07:57 +0000
> 
> > This patchset, intended for 2.6.30, converts all in-tree arm platforms 
> > from smc911x to the actively maintained smsc911x driver.
> > 
> > I don't have any of these platforms available to me, so I've only been 
> > able to compile-test the changes.
> > 
> > David Miller is planning to take the smsc911x patches via net-2.6, but 
> > I've included them here to make testing easier as the other patches in 
> > the set depend on them.
> > 
> > This patchset supercedes previous irq_flags patches from me and Stanley 
> > Miao.
> 
> I've applied patches 1 and 2, the smsc911x driver changes.
> 
> I can pull the platform changes into net-next-2.6 as well
> if people don't think there will enough conflicts to cause
> problems.

I think  the platform data had better stay in arm tree.

Stanley.
--
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