From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, zippel@linux-m68k.org
Subject: Re: [RFC/POC] multiple CONFIG y/m/n
Date: Sat, 08 Apr 2006 00:04:26 +0900 [thread overview]
Message-ID: <87odzdh1fp.fsf@duaron.myhome.or.jp> (raw)
In-Reply-To: <20060406224134.0430e827.rdunlap@xenotime.net> (Randy Dunlap's message of "Thu, 6 Apr 2006 22:41:34 -0700")
"Randy.Dunlap" <rdunlap@xenotime.net> writes:
> As it is here, PARPORT_ENABLE_ALL tracks PARPORT (y/m/n) when the former
> is enabled/configured. The downside of this Kconfig usage is that almost
> all lines of "depends" are duplicated as "select" (and that it uses "select").
> It would be good if there was some way to automate this.
>
> Comments?
Umm... Oh, how about the following? It seems work...
$ perl -spi -e 's/CONFIG_SND.*//' .config
$ KCONFIG_ALLCONFIG=.config make allmodconfig or allyesconfig
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2006-04-07 15:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 5:41 [RFC/POC] multiple CONFIG y/m/n Randy.Dunlap
2006-04-07 15:04 ` OGAWA Hirofumi [this message]
2006-04-07 15:45 ` Randy.Dunlap
2006-04-10 5:04 ` Randy.Dunlap
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=87odzdh1fp.fsf@duaron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.