mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Giacomo A. Catenazzi" <cate@cateee.net>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: diet-kconfig: a script to trim unneeded kconfigs
Date: Thu, 18 Sep 2008 22:20:31 +0200	[thread overview]
Message-ID: <s5hiqsturxs.wl%tiwai@suse.de> (raw)
In-Reply-To: <48D27734.3040600@cateee.net>

At Thu, 18 Sep 2008 17:43:48 +0200,
Giacomo A. Catenazzi wrote:
> 
> Mauro Carvalho Chehab wrote:
> > Hi Takashi,
> > 
> > On Wed, 17 Sep 2008 01:55:26 +0200
> > Takashi Iwai <tiwai@suse.de> wrote:
> 
> >> The script is VERY hackish.  I should have begun with perl or whatever
> >> better script language, but I chose bash and co.  So, don't expect
> >> much code quality.  I'm no script guy after all :)
> > 
> > Using just a shellscript and binutils seems to be better than using other
> > tools, since it allows the usage on minimal configured systems where the user
> > might not have perl or other scripting languages.
> 
> But very slow, complex and not enough powerful:
> The tools should have extensive knowledge about Kconfig,
> and the CONFIG_ dependencies; it should handle a lot of
> structures (text/binary; line/record oriented; etc.), which
> it is not easy in shell (awk, od, sed with extended regexp are
> not core utilities).

It's not that slow.

> So my suggestion is: do it in a high level language, to find and
> stabilize the design, and then integrate it in kconfig later (using
> C).

Maybe a good idea to add such functionality into kbuild itself.
It's THE parser after all.


thanks,

Takashi

  parent reply	other threads:[~2008-09-18 20:20 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
2008-09-23 19:40                       ` Chris Li
2008-09-18 20:20     ` Takashi Iwai [this message]
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=s5hiqsturxs.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=cate@cateee.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.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®