From: Takashi Iwai <tiwai@suse.de>
To: "Chris Li" <lkml@chrisli.org>
Cc: "Giacomo A. Catenazzi" <cate@cateee.net>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: diet-kconfig: a script to trim unneeded kconfigs
Date: Tue, 23 Sep 2008 20:50:48 +0200 [thread overview]
Message-ID: <s5hhc86ae7r.wl%tiwai@suse.de> (raw)
In-Reply-To: <70318cbf0809231115r506db98etd87b67a590ba6eae@mail.gmail.com>
At Tue, 23 Sep 2008 11:15:19 -0700,
Chris Li wrote:
>
> On Tue, Sep 23, 2008 at 4:31 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > That is true. Enabling arbitrary kernel config item is hard to
> > achieve right now. I think this feature should be implemented in
> > kbuild parser itself. The current reverse-select is way limited and
> > known to be problematic in many kernel configs.
>
> I was looking at the kbuild system. BTW, I really like the Makefile
> in kbuild. For the reverse select, here is what I have in mind.
>
> The reverse select needs to maintain the define-user chain for
> each kernel option. And each kernel option has a list of the kernel
> option and value pare to enable an option. Once we produce such
> an list for "all config". We can know exactly what kernel option
> needs to set in order to get to so module. It is kind of doing
> the data flow analyze on the config options.
>
> It is not trivial, but it shouldn't be too hard either.
Well, it is not so easy, too.
The good-working reverse selection with dependency checks is a
feature we've long for in Kconfig, but it hasn't been implemented
because it could easily introduce a messy dependency loop, or some
cases are not easily resolvable.
Anyway, the development of reverse-selection should involve with Sam
and other Kbuild maintainer/developers.
Takashi
next prev parent reply other threads:[~2008-09-23 18:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 23:55 Takashi Iwai
2008-09-18 14:01 ` Giacomo A. Catenazzi
2008-09-18 20:09 ` Takashi Iwai
2008-09-18 15:25 ` Mauro Carvalho Chehab
2008-09-18 15:43 ` Giacomo A. Catenazzi
2008-09-18 16:27 ` Mauro Carvalho Chehab
2008-09-19 9:12 ` Giacomo A. Catenazzi
2008-09-19 16:01 ` Takashi Iwai
2008-09-19 23:55 ` Chris Li
2008-09-19 23:57 ` Chris Li
2008-09-22 10:01 ` Takashi Iwai
2008-09-22 13:39 ` Giacomo A. Catenazzi
2008-09-22 15:41 ` Steven Rostedt
2008-09-22 15:50 ` Takashi Iwai
2008-09-22 19:25 ` Chris Li
2008-09-23 11:31 ` Takashi Iwai
2008-09-23 18:15 ` Chris Li
2008-09-23 18:50 ` Takashi Iwai [this message]
2008-09-23 19:40 ` Chris Li
2008-09-18 20:20 ` Takashi Iwai
2008-09-18 20:17 ` Takashi Iwai
2008-09-18 21:09 ` Valdis.Kletnieks
2008-09-18 22:14 ` Takashi Iwai
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=s5hhc86ae7r.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=cate@cateee.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@chrisli.org \
--cc=mchehab@infradead.org \
--cc=rostedt@goodmis.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®