From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: fixes for 3.9-rc #2
Date: Tue, 26 Mar 2013 11:56:43 +0100 [thread overview]
Message-ID: <51517EEB.7030709@atmel.com> (raw)
In-Reply-To: <201303261022.39882.arnd@arndb.de>
On 03/26/2013 11:22 AM, Arnd Bergmann :
> 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
Yes, fine, I stack them for 3.10 then.
> , 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.
Indeed, at first sight its looks like a nice solution. But I wonder if
we add several nodes in this kind of .dtsi files, we may end up with
mess between APB peripherals and board specific ones like leds, NAND, etc.
Moreover, the plain and full naming of the node makes it identifiable
without doubts, even someone not completely familiar with DT.
I slightly prefer to keep it like this, but I can still change my mind ;-)
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2013-03-26 10:56 UTC|newest]
Thread overview: 5+ 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:22 ` Arnd Bergmann
2013-03-26 10:56 ` Nicolas Ferre [this message]
2013-03-26 11:05 ` Arnd Bergmann
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=51517EEB.7030709@atmel.com \
--to=nicolas.ferre@atmel.com \
--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 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).