[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a781481a0705200438s634712e6v957d7085bca7407@mail.gmail.com>
Date: Sun, 20 May 2007 17:08:52 +0530
From: "Satyam Sharma" <satyam.sharma@...il.com>
To: "Stefan Richter" <stefanr@...6.in-berlin.de>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Sam Ravnborg" <sam@...nborg.org>,
LKML <linux-kernel@...r.kernel.org>,
"Roman Zippel" <zippel@...ux-m68k.org>,
"Kumar Gala" <galak@...nel.crashing.org>,
"Simon Horman" <horms@...ge.net.au>, "Adrian Bunk" <bunk@...sta.de>
Subject: Re: RFC: kconfig select warnings bogus?
On 5/20/07, Stefan Richter <stefanr@...6.in-berlin.de> wrote:
> Satyam Sharma wrote:
> > You'll learn about the "default .. if .." Kconfig idiom after you try
> > this,
>
> I have seen these in the rest of the patch which I didn't quote.
>
> However you fix it --- don't remove "depends on" or "select". You can
> interchange them, but not remove them, unless there wasn't a dependency
> to begin with.
They _can_ be removed, with absolutely no build failures at all, because
of the "default y if ..." on the dependency that is defined in some
arch/.../Kconfig.
In fact the whole _idea_ is to remove any mention of the arch-specific
dependency from arch-agnostic stuff in drivers/.../Kconfig's (be it
"depends" or "select") so as not to generate those "unknown symbols"
warnings that would come on other archs. Hence, the normal practice to
use the "default y if ..." idiom (for "bool" helper code like the original
examples on this thread) in arch/.../Kconfig files.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists