linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7: Rebuild default configuration on v4.3-rc1
Date: Wed, 16 Sep 2015 17:57:08 +0100	[thread overview]
Message-ID: <20150916165708.GG21084@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <7h37yegwpw.fsf@deeprootsystems.com>

On Wed, Sep 16, 2015 at 09:22:51AM -0700, Kevin Hilman wrote:
> As one of the maintainers of multi_v7_defconfig, I'm fully supportive of

As ARM maintainer...

> avoiding the growing cruftyness of this file, and making it more
> maintainable, especially because we have a better opportunity to enforce
> it.  IMO, there's a big difference between churn and cleanup for better
> maintainability.

Moving options around (which is the majority of what this patch does)
is not cruftyness.  It's a fact of life that changes to the Kconfig
files change the order of configuration options all the time.  It's
got nothing to do with the order that the options appear.  Just adding
another dependency can change the ordering.

I've no problem with adding and removing options where it's appropriate
to do so.  What I have a problem with is all the needless churn such as
in this patch, where options are moved from one place to another without
any benefit what so ever.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

      reply	other threads:[~2015-09-16 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 10:51 [PATCH] ARM: multi_v7: Rebuild default configuration on v4.3-rc1 Thierry Reding
2015-09-15 11:12 ` Russell King - ARM Linux
2015-09-15 13:46   ` Thierry Reding
2015-09-15 14:23     ` Russell King - ARM Linux
2015-09-15 15:23       ` Thierry Reding
2015-09-16 16:22         ` Kevin Hilman
2015-09-16 16:57           ` Russell King - ARM Linux [this message]

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=20150916165708.GG21084@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).