netdev - Re: [PATCH 0/5] NET: PHY names vs MDIO bus names regression fixes

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: <20120213.160204.622185887026096350.davem@davemloft.net>
Date:	Mon, 13 Feb 2012 16:02:04 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	florian@...nwrt.org
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 0/5] NET: PHY names vs MDIO bus names regression fixes

From: Florian Fainelli <florian@...nwrt.org>
Date: Mon, 13 Feb 2012 12:23:19 +0100

> This patch serie aims at fixing the regressions introduced with the
> "use an unique MDIO bus name" patchset. Some drivers still formatted
> the PHY id to use the old bus name (e.g: "0" or "1") and therefore
> the PHY probing logic gets broken because their underlying MDIO bus
> name was changed too from "0" to <foo>-<id>.
> 
> The offending patches got introduced during 3.3-rc1.

Then why the heck are you CC:'ing -stable on these patches?

We're still in the 3.3-rcX phase, so there is no other tree in
the world these patches should be applied to.

In any event, for networking stuff, you shouldn't be adding
the stable CC: anyways, I take care of all networking stable
submissions myself.
--
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