From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC [PATCH 2/9] Initial makefiles and Kconfigs for the lcp32xx mach
Date: Sat, 21 Nov 2009 09:34:07 +0000 [thread overview]
Message-ID: <20091121093407.GC7998@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02BBC43ACB@dbde02.ent.ti.com>
On Sat, Nov 21, 2009 at 02:52:29PM +0530, Shilimkar, Santosh wrote:
> I think it does warn with some thing like
> warning: override: reassigning to symbol XXXXX
It's silent, because there are situations you do want to override other
symbols - eg, FRAME_POINTER. This isn't a problem because the ARM
Kconfigs don't get included into non-ARM builds.
However, all sub-architecture Kconfigs are included for all ARM Kconfig
runs, which means the contents of them can potentially be affected by
each other. We need be disciplined and only have configuration options
defined at one level - if they are already defined in arch/arm/Kconfig,
then they should not be redefined in any arch/arm/*/Kconfig*.
prev parent reply other threads:[~2009-11-21 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 1:11 RFC [PATCH 2/9] Initial makefiles and Kconfigs for the lcp32xx mach Kevin Wells
2009-11-21 9:01 ` Russell King - ARM Linux
2009-11-21 9:22 ` Shilimkar, Santosh
2009-11-21 9:34 ` 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=20091121093407.GC7998@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