All of lore.kernel.org
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: The Alphabet (or, the sorting of Kconfig symbols)
Date: Tue, 8 Apr 2014 20:52:25 +0200	[thread overview]
Message-ID: <20140408185225.GU29751@pengutronix.de> (raw)
In-Reply-To: <CACxGe6uoB6CkuV7HCg8wdyu2Tm471YaAz0sDA3W2C0MPAYYY+Q@mail.gmail.com>

On Fri, Apr 04, 2014 at 04:24:27AM -0700, Grant Likely wrote:
> On Fri, Apr 4, 2014 at 4:16 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > For those who don't know it, the order of letters in the alphabet is:
> >
> > A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
> >
> > and we use this order to determine the position of "select" entries in
> > Kconfig files.  We do that so that we can reduce conflicts.  Conflicts
> > such as these kinds of rubbish:
> 
> Equally applies to #include ordering.
With #includes there might be exceptions though because of dependencies
between headers.
I don't know how common these are today, I didn't have had dependency
problems for some time now, but I wouldn't want checkpatch to treat the
order of #includes as error, while for Kconfig it's fine.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  parent reply	other threads:[~2014-04-08 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 11:16 The Alphabet (or, the sorting of Kconfig symbols) Russell King - ARM Linux
2014-04-04 11:22 ` Russell King - ARM Linux
2014-04-04 11:24 ` Grant Likely
2014-04-04 12:11   ` Richard Cochran
2014-04-04 12:55     ` Christopher Covington
2014-04-08 13:55     ` Laurent Pinchart
2014-04-08 18:52   ` Uwe Kleine-König [this message]
2014-04-08 20:21     ` Richard Cochran
2014-04-08 21:05       ` Sergei Shtylyov

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=20140408185225.GU29751@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.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.