netdev - Re: [PATCH 3/3] smsc911x: add flag SMSC911X_USE

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] [day] [month] [year] [list]

Message-Id: <20090324.021826.102378372.davem@davemloft.net>
Date:	Tue, 24 Mar 2009 02:18:26 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linuxzsc@...il.com
Cc:	steve.glendinning@...c.com, netdev@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, kernel@...gutronix.de
Subject: Re: [PATCH 3/3] smsc911x: add flag SMSC911X_USE_INTERPHY

From: Richard Zhao <linuxzsc@...il.com>
Date: Tue, 24 Mar 2009 16:36:08 +0800

> On Tue, Mar 24, 2009 at 3:51 PM, Sascha Hauer <s.hauer@...gutronix.de> wrote:
> > Hi Richard,
> >
> > On Tue, Mar 24, 2009 at 02:47:25PM +0800, Richard Zhao wrote:
> >> mx31pdk board don't have external PHY, but it wrongly pull up MDIO.
> >> So, add flag SMSC911X_USE_INTERPHY to force using internal PHY.
> >
> > This patch is outdated. Linux-next already contains a
> > SMSC911X_FORCE_INTERNAL_PHY for exactly this reason.
> >
> > Sascha
> >
> Hi Sascha,
> 
> Sorry I didn't check linux-next. Do I need always to create mxc
> patches based on linux-nex?
> And I don't know why the smsc911x patch commited on Feb 1 on
> linux-next still not be merged to mainline?

Because it was not a critical regression fix, so it goes
to net-next-2.6 until the merge window opens up.
--
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