All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Philip Prindeville <philipp@redfish-solutions.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Parsing kconfig files from scripts
Date: Sat, 14 Jan 2012 21:58:39 +0100	[thread overview]
Message-ID: <4F11EC7F.4060506@suse.cz> (raw)
In-Reply-To: <4F10AE71.1060804@redfish-solutions.com>

On 13.1.2012 23:21, Philip Prindeville wrote:
> One of the tasks on my list is to build automation that detects what
> targets to build nightly after continuous integrations into SCM
> (including new platforms being added).
> 
> A way to do this is to find in the Kconfig tree all possible values
> of a given symbol, such as CONFIG_CMDLINE for instance (ok, not a
> great example).
> 
> I was wondering if there was a command-line utility one could invoke
> to query the parse tree and dump values from it.

There is not, but a patch adding such tool would be welcome.

Michal

      reply	other threads:[~2012-01-14 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 22:21 Parsing kconfig files from scripts Philip Prindeville
2012-01-14 20:58 ` Michal Marek [this message]

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=4F11EC7F.4060506@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=philipp@redfish-solutions.com \
    /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.