From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org, sam@ravnborg.org
Subject: Re: [RFC/POC] multiple CONFIG y/m/n
Date: Sun, 9 Apr 2006 22:04:26 -0700 [thread overview]
Message-ID: <20060409220426.8027953a.rdunlap@xenotime.net> (raw)
In-Reply-To: <87odzdh1fp.fsf@duaron.myhome.or.jp>
On Sat, 08 Apr 2006 00:04:26 +0900 OGAWA Hirofumi wrote:
> "Randy.Dunlap" <rdunlap@xenotime.net> writes:
>
> > Comments?
>
> Umm... Oh, how about the following? It seems work...
>
> $ perl -spi -e 's/CONFIG_SND.*//' .config
> $ KCONFIG_ALLCONFIG=.config make allmodconfig or allyesconfig
Hrm, that points out a lack of documentation for this feature.
Would the kconfig/kbuild people prefer this documentation in the source
code (see below) or in Documentation/kbuild/somefile ?
---
---
scripts/kconfig/conf.c | 22 ++++++++++++++++++++--
1 files changed, 20 insertions(+), 2 deletions(-)
--- linux-2617-rc1.orig/scripts/kconfig/conf.c
+++ linux-2617-rc1/scripts/kconfig/conf.c
@@ -504,6 +504,24 @@ static void check_conf(struct menu *menu
check_conf(child);
}
+void usage(char *progname)
+{
+ printf("%s [-o|-s|-d|-D|-n|-m|-y|-r] Kconfig_filename\n", progname);
+ printf(" -o: oldconfig: ask only about new config symbols\n");
+ printf(" -s: silentoldconfig: don't ask about any symbol values\n");
+ printf(" -d: defconfig: use default symbol values\n");
+ printf(" -D: use default symbol values from the specified config file\n");
+ printf(" -n: set unknown symbol values to 'n'\n");
+ printf(" -m: set unknown symbol values to 'm'\n");
+ printf(" -y: set unknown symbol values to 'y'\n");
+ printf(" -r: set unknown symbol values randomly to one of y/m/n\n");
+ printf("The n/m/y/r options can also use the environment variable KCONFIG_ALLCONFIG\n");
+ printf(" to specify a filename that contains config options that are\n");
+ printf(" to be set to a specific value. Otherwise config checks for\n");
+ printf(" all{no,mod,yes,random}.config and all.config\n");
+ exit(0);
+}
+
int main(int ac, char **av)
{
int i = 1;
@@ -546,8 +564,8 @@ int main(int ac, char **av)
break;
case 'h':
case '?':
- printf("%s [-o|-s] config\n", av[0]);
- exit(0);
+ usage(av[0]);
+ break;
}
}
name = av[i];
next prev parent reply other threads:[~2006-04-10 5:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 5:41 Randy.Dunlap
2006-04-07 15:04 ` OGAWA Hirofumi
2006-04-07 15:45 ` Randy.Dunlap
2006-04-10 5:04 ` Randy.Dunlap [this message]
2006-04-12 11:00 ` Roman Zippel
2006-04-12 16:17 ` Randy.Dunlap
2006-04-12 16:59 ` Sam Ravnborg
2006-04-12 18:56 ` [PATCH] config: update usage/help info Randy.Dunlap
2006-04-12 20:44 ` Sam Ravnborg
2006-04-07 18:44 ` [RFC/POC] multiple CONFIG y/m/n Sam Ravnborg
2006-04-07 21:24 ` Roman Zippel
2006-04-07 21:36 ` Randy.Dunlap
2006-04-11 11:05 ` Jan Engelhardt
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=20060409220426.8027953a.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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®