From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: fixes for 3.9-rc #2
Date: Tue, 26 Mar 2013 10:22:39 +0000 [thread overview]
Message-ID: <201303261022.39882.arnd@arndb.de> (raw)
In-Reply-To: <51517592.5010300@atmel.com>
On Tuesday 26 March 2013, Nicolas Ferre wrote:
> Another "fixes" pull-request for AT91 on top of material that you have already
> taken. Fixes are manly typos but the bad node declaration and some misspelling
> can cause confusion.
Hi Nicolas,
I'd prefer to take only fixes for serious bugs into 3.9 now, since I have
already sent the fixes for -rc5. As far as I can tell, the macb node patch
is the only one that falls into that category, but for that one, I'd
prefer if it could be redone in a simpler way, by replacing
+ ahb {
+ apb {
+ macb0: ethernet at f802c000 {
+ phy-mode = "rmii";
+ status = "okay";
+ };
+ };
+ };
with
@macb0 {
phy-mode = "rmii";
status = "okay";
}
as there is no need to provide the full path when you already have
a label for the device.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Olof Johansson <olof@lixom.net>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
"linux-arm-kernel" <linux-arm-kernel@lists.infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] at91: fixes for 3.9-rc #2
Date: Tue, 26 Mar 2013 10:22:39 +0000 [thread overview]
Message-ID: <201303261022.39882.arnd@arndb.de> (raw)
In-Reply-To: <51517592.5010300@atmel.com>
On Tuesday 26 March 2013, Nicolas Ferre wrote:
> Another "fixes" pull-request for AT91 on top of material that you have already
> taken. Fixes are manly typos but the bad node declaration and some misspelling
> can cause confusion.
Hi Nicolas,
I'd prefer to take only fixes for serious bugs into 3.9 now, since I have
already sent the fixes for -rc5. As far as I can tell, the macb node patch
is the only one that falls into that category, but for that one, I'd
prefer if it could be redone in a simpler way, by replacing
+ ahb {
+ apb {
+ macb0: ethernet@f802c000 {
+ phy-mode = "rmii";
+ status = "okay";
+ };
+ };
+ };
with
@macb0 {
phy-mode = "rmii";
status = "okay";
}
as there is no need to provide the full path when you already have
a label for the device.
Arnd
next prev parent reply other threads:[~2013-03-26 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 10:16 [GIT PULL] at91: fixes for 3.9-rc #2 Nicolas Ferre
2013-03-26 10:16 ` Nicolas Ferre
2013-03-26 10:22 ` Arnd Bergmann [this message]
2013-03-26 10:22 ` Arnd Bergmann
2013-03-26 10:56 ` Nicolas Ferre
2013-03-26 10:56 ` Nicolas Ferre
2013-03-26 11:05 ` Arnd Bergmann
2013-03-26 11:05 ` Arnd Bergmann
2013-03-27 11:28 ` Nicolas Ferre
2013-03-27 11:28 ` Nicolas Ferre
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=201303261022.39882.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.