public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: GENERIC still failing?
Date: Wed, 15 Oct 2003 02:40:44 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106618574212827@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106617635106445@msgid-missing>

On Wed, 15 Oct 2003 12:15:48 +1000 Ian Wienand <ianw@gelato.unsw.edu.au> wrote:

| On Tue, Oct 14, 2003 at 05:22:05PM -0700, Jesse Barnes wrote:
| > Looks like CONFIG_NUMA and CONFIG_DISCONTIGMEM are missing from the
| > config being built.  A generic kernel won't work without them.
| 
| mea culpa, as usual. Is there some way to make it when you select
| generic it always requires CONFIG_NUMA/DISCONTIGMEM?

Yes, use "select" (see Documentation/kbuild/kconfig-language.txt).
E.g.,

config GENERIC
	bool "blah"
	select NUMA
	select DISCONTIGMEM
	---help---


| Also, trying to look at the help text, it seems that the sub-items of
| a 'choice' in Kconfig can't have individual help texts?
| 
| For example 
|  
| choice
| 	prompt "IA-64 processor type"
| 	---help---
| 	 this will show when you select help on 'IA-64 processor type'
| config ITANIUM
| 	bool "Itanium"
| 	---help---
| 	 this text appears not to show when you select help on 'Itanium' 
| 	 in the choice.
| endchoice
| 
| I'm not sure if this is the desired effect, but certainly some of the
| help texts appear mis-placed under an option of the choice rather than
| at the choice it's self (see attached for example).

--
~Randy

  parent reply	other threads:[~2003-10-15  2:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15  0:05 GENERIC still failing? David Mosberger
2003-10-15  0:12 ` Jesse Barnes
2003-10-15  0:22 ` Jesse Barnes
2003-10-15  0:56 ` David Mosberger
2003-10-15  0:57 ` David Mosberger
2003-10-15  2:15 ` Ian Wienand
2003-10-15  2:40 ` Randy.Dunlap [this message]
2003-10-15  3:03 ` Jesse Barnes
2003-10-15 11:24 ` Matthew Wilcox
2003-10-15 23:14 ` Ian Wienand

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=marc-linux-ia64-106618574212827@msgid-missing \
    --to=rddunlap@osdl.org \
    --cc=linux-ia64@vger.kernel.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