netdev - Re: [STABLE][3.0][3.2][Add PATCH] phy/fixed: use an unique MDIO bus name

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20121007.145622.83624305358947187.davem@davemloft.net>
Date:	Sun, 07 Oct 2012 14:56:22 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	ben@...adent.org.uk
Cc:	rostedt@...dmis.org, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org, gregkh@...uxfoundation.org,
	florian@...nwrt.org, netdev@...r.kernel.org
Subject: Re: [STABLE][3.0][3.2][Add PATCH] phy/fixed: use an unique MDIO
 bus name

From: Ben Hutchings <ben@...adent.org.uk>
Date: Sun, 07 Oct 2012 16:33:39 +0100

> Networking stable fixes are normally vetted, backported and bundled up
> by David, so I'll let him decide on this.
> 
> There are a lot more MDIO bus drivers that don't play nicely with
> others, most of which seem to be fixed in mainline.  If David agrees
> that these are generally worthwhile then perhaps someone could try to
> gather those up?

I very much am not inclined to backport this stuff, it impacts
an extremely small group of people so the risk/benefit ratio is
simply not worth it for me to do the work.

If someone else does the work and tests it, I'm willing to ACK
it going into -stable.

But this change impacted a lot of MDIO drivers and there were
regressions that needed to be fixed up the first time this stuff
went in.
--
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