linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH v2 4/9] arm: dts: sun8i: split Allwinner H3 .dtsi
Date: Fri, 27 Jan 2017 22:10:29 +0100	[thread overview]
Message-ID: <20170127211029.k5ylfhrreqfdn2iz@lukather> (raw)
In-Reply-To: <20170127190239.2MQaUuKh@smtp2o.mail.yandex.net>

On Sat, Jan 28, 2017 at 12:02:20AM +0800, Icenowy Zheng wrote:
> 
> 2017?1?27? 23:55? Maxime Ripard <maxime.ripard@free-electrons.com>???
> >
> > On Thu, Jan 26, 2017 at 11:48:54PM +0800, Icenowy Zheng wrote: 
> > > - mmc0: mmc at 01c0f000 { 
> > > + mmc at 01c0f000 { 
> >
> > There's no point in removing the labels, and you can even use the 
> > label-based syntax to reference them, instead of using the path. 
> 
> I think keeping a tree structure in sub dtsi file will make it more
> pretty and easy to use :-)

We're already using that syntax for all the DTS, so it won't be less
pretty than those.

And keeping a tree structure valid is not easier to use than, well,
not having to keep it.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170127/ae35c7ca/attachment.sig>

           reply	other threads:[~2017-01-27 21:10 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170127190239.2MQaUuKh@smtp2o.mail.yandex.net>]

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=20170127211029.k5ylfhrreqfdn2iz@lukather \
    --to=maxime.ripard@free-electrons.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).