From: Arnd Bergmann <arnd@arndb.de>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Florian Fainelli <florian@openwrt.org>,
linux-arm-kernel@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel <kernel@pengutronix.de>,
"shawn.guo" <shawn.guo@linaro.org>,
David Miller <davem@davemloft.net>,
Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: Re: [PATCHv2 1/3] net: phy: prevent linking breakage
Date: Wed, 5 Jun 2013 13:21:00 +0200 [thread overview]
Message-ID: <201306051321.00264.arnd@arndb.de> (raw)
In-Reply-To: <51AF03AF.3080106@free-electrons.com>
On Wednesday 05 June 2013, Alexandre Belloni wrote:
> However, it is becoming urgent for Atmel to get the fix in 3.10 so that
> they never get a kernel compilation that breaks.
I don't think it's urgent since this is only about rare configurations,
and not a regression. We can queue the patch "ARM: at91: Fix link
breakage when !CONFIG_PHYLIB" you just sent to fix this, but I
would not consider it a serious problem to have it only in 3.11.
Arnd
next prev parent reply other threads:[~2013-06-05 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 11:43 [PATCHv2 0/3] net: phy: prevent linking breakage Alexandre Belloni
2013-05-28 11:43 ` [PATCHv2 1/3] " Alexandre Belloni
2013-05-28 20:09 ` David Miller
2013-05-29 8:21 ` Alexandre Belloni
2013-05-30 9:42 ` David Miller
2013-06-04 15:07 ` Arnd Bergmann
2013-06-04 15:36 ` Florian Fainelli
2013-06-04 16:01 ` Arnd Bergmann
2013-06-04 16:09 ` Florian Fainelli
2013-06-04 17:17 ` Arnd Bergmann
2013-06-05 9:23 ` Alexandre Belloni
2013-06-05 11:21 ` Arnd Bergmann [this message]
2013-05-28 11:43 ` [PATCHv2 2/3] arm: mxs: don't check for CONFIG_PHYLIB as builtin Alexandre Belloni
2013-05-28 11:43 ` [PATCHv2 3/3] arm: imx: " Alexandre Belloni
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=201306051321.00264.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=davem@davemloft.net \
--cc=florian@openwrt.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=shawn.guo@linaro.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