From: linux@arm.linux.org.uk (Russell King - ARM Linux)
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:49:18 +0100 [thread overview]
Message-ID: <20101022074918.GA25606@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1287686255-18674-1-git-send-email-dwalker@codeaurora.org>
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.
Plus it increases the file count, makes things more indirect, and
therefore harder to follow.
next prev parent reply other threads:[~2010-10-22 7:49 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 [this message]
2010-10-22 15:20 ` Daniel Walker
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=20101022074918.GA25606@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).