linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm: msm: moved Kconfig machine entry into mach-msm
Date: Fri, 22 Oct 2010 08:20:00 -0700	[thread overview]
Message-ID: <1287760800.18266.5.camel@m0nster> (raw)
In-Reply-To: <20101022074918.GA25606@n2100.arm.linux.org.uk>

On Fri, 2010-10-22 at 08:49 +0100, Russell King - ARM Linux wrote:
> On Thu, Oct 21, 2010 at 11:37:35AM -0700, Daniel Walker wrote:
> > Has anyone suggested this? It seems like it might reduce conflicts
> > in the Kconfig file.
> 
> How?  The choice normally has one entry for each mach- directory.
> You're still going to have 'source' for each mach- directory, so
> the chances of conflicts are no different.

The source lines would be mostly static.. We wouldn't have to modify
Kconfig to add new "select" statements to are entries. People end up
having to send you patches which do something then modify the Kconfig
(or in some cases they don't send them to you which is worse) in order
to reduce conflicts. With this change they wouldn't need to do that.

> Plus it increases the file count, makes things more indirect, and
> therefore harder to follow.

True. It's a trade off , but we already have this for the other menu
options further down the Kconfig.

Daniel
-- 
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum.

  reply	other threads:[~2010-10-22 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 18:37 [RFC PATCH] arm: msm: moved Kconfig machine entry into mach-msm Daniel Walker
2010-10-22  7:49 ` Russell King - ARM Linux
2010-10-22 15:20   ` Daniel Walker [this message]
2010-10-22 15:25     ` Russell King - ARM Linux

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=1287760800.18266.5.camel@m0nster \
    --to=dwalker@codeaurora.org \
    --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).