From: Randy Dunlap <rdunlap@xenotime.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Peter Foley <pefoley2@verizon.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 2/2] init/Kconfig: use if/endif to surround the EXPERT menu kconfig symbols
Date: Wed, 27 Apr 2011 07:42:23 -0700 [thread overview]
Message-ID: <20110427074223.9309ac0b.rdunlap@xenotime.net> (raw)
In-Reply-To: <BANLkTimsFd-LfT6wF-iYPY7TNqR0q388XA@mail.gmail.com>
On Wed, 27 Apr 2011 09:56:06 +0200 Geert Uytterhoeven wrote:
> On Wed, Apr 27, 2011 at 01:09, David Rientjes <rientjes@google.com> wrote:
> > On Tue, 26 Apr 2011, Randy Dunlap wrote:
> >
> >> From: Randy Dunlap <randy.dunlap@oracle.com>
> >>
> >> Surround the EXPERT menu with "if EXPERT" and "endif" so that it
> >> is forced to stay as one unit. Hopefully this will help to prevent
> >> it being broken in the future.
> >>
> >> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> >> Cc: David Rientjes <rientjes@google.com>
> >> Cc: Peter Foley <pefoley2@verizon.net>
> >> ---
> >> init/Kconfig | 36 ++++++++++++++++++++----------------
> >> 1 file changed, 20 insertions(+), 16 deletions(-)
> >>
> >> --- lnx-2639-rc4.orig/init/Kconfig
> >> +++ lnx-2639-rc4/init/Kconfig
> >> @@ -924,15 +924,17 @@ menuconfig EXPERT
> >> environments which can tolerate a "non-standard" kernel.
> >> Only use this if you really know what you are doing.
> >>
> >> +if EXPERT
> >> +
> >> config UID16
> >> - bool "Enable 16-bit UID system calls" if EXPERT
> >> + bool "Enable 16-bit UID system calls"
> >> depends on ARM || BLACKFIN || CRIS || FRV || H8300 || X86_32 || M68K || (S390 && !64BIT) || SUPERH || SPARC32 || (SPARC64 && COMPAT) || UML || (X86_64 && IA32_EMULATION)
> >> default y
> >> help
> >> This enables the legacy 16-bit UID syscall wrappers.
> >>
> >
> > I don't like this, people who look up a Kconfig option typically only
> > look at the single entry and look for dependencies within it, not the
> > context in which it is declared in the Kconfig file.
>
> What about extracting the part that depends on EXPERT into its own file
> init/Kconfig.expert?
>
> Using separate Kconfig.xxx files could become a Kconfig pattern...
Yes, I thought of that last night also. Yes, it could help.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-04-27 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 20:00 Randy Dunlap
2011-04-26 23:09 ` David Rientjes
2011-04-26 23:15 ` Randy Dunlap
2011-04-27 7:56 ` Geert Uytterhoeven
2011-04-27 14:42 ` Randy Dunlap [this message]
2011-04-27 3:02 ` Mike Frysinger
2011-04-27 23:14 ` Andrew Morton
2011-04-28 2:36 ` Randy Dunlap
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=20110427074223.9309ac0b.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@verizon.net \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®