From: David Miller <davem@davemloft.net>
To: florian@openwrt.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] NET: PHY names vs MDIO bus names regression fixes
Date: Mon, 13 Feb 2012 16:02:04 -0500 (EST) [thread overview]
Message-ID: <20120213.160204.622185887026096350.davem@davemloft.net> (raw)
In-Reply-To: <1329132204-27946-1-git-send-email-florian@openwrt.org>
From: Florian Fainelli <florian@openwrt.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.
next prev parent reply other threads:[~2012-02-13 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 11:23 [PATCH 0/5] NET: PHY names vs MDIO bus names regression fixes Florian Fainelli
2012-02-13 11:23 ` [PATCH 1/5] cpmac: fix PHY name to match MDIO bus name Florian Fainelli
2012-02-13 11:23 ` [PATCH 2/5] bcm63xx-enet: " Florian Fainelli
2012-02-13 11:23 ` [PATCH 3/5] fec: fix PHY name to match fixed " Florian Fainelli
2012-02-13 11:23 ` [PATCH 4/5] octeon: fix PHY name to match " Florian Fainelli
2012-02-13 11:23 ` [PATCH 5/5] ixp4xx-eth: " Florian Fainelli
2012-02-13 21:02 ` David Miller [this message]
2012-02-13 22:00 ` [PATCH 0/5] NET: PHY names vs MDIO bus names regression fixes Florian Fainelli
2012-02-13 23:43 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120213.160204.622185887026096350.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=florian@openwrt.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).