linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: boot: dts: add DTS for Baltos IR5221
Date: Wed, 13 May 2015 08:50:12 -0700	[thread overview]
Message-ID: <20150513155012.GI15563@atomide.com> (raw)
In-Reply-To: <20150513152904.GC4201@saruman.tx.rr.com>

* Felipe Balbi <balbi@ti.com> [150513 08:32]:
> On Wed, May 13, 2015 at 07:40:02AM +0200, Lothar Wa?mann wrote:
> > >
> > Should these be ordered alphabetically?
> 
> why ?

In general the alphabetical ordering helps to avoid merge
conflicts when new things are added later on as they are
not all added to the end. So yeah I have a slight sorting
preference there too to make my life easier in the future :)

Regards,

Tony

  parent reply	other threads:[~2015-05-13 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 22:15 [PATCH] arm: boot: dts: add DTS for Baltos IR5221 Felipe Balbi
2015-05-13  5:40 ` Lothar Waßmann
2015-05-13 15:29   ` Felipe Balbi
2015-05-13 15:37     ` Yegor Yefremov
2015-05-13 15:50     ` Tony Lindgren [this message]
2015-05-19  8:33       ` Yegor Yefremov

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=20150513155012.GI15563@atomide.com \
    --to=tony@atomide.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).