public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: scripted kconfig replies?
Date: Fri, 03 Dec 2010 14:37:25 +0100	[thread overview]
Message-ID: <4CF8F295.6050205@suse.cz> (raw)
In-Reply-To: <4CF8F169.7050008@suse.cz>

On 3.12.2010 14:32, Michal Marek wrote:
> On 22.11.2010 05:46, Randy Dunlap wrote:
>> Hi,
>>
>> I'd like to be able to write a script that handles 'make oldconfig'
>> queries for unknown kconfig symbols.  The script would take options
>> like:  set all tristate prompts to one of y/m/n, set all boolean prompts
>> to one of y/n.  (and just use defaults for numeric or string symbols)
>>
>> This would allow me to automate some kernel configs.  I don't think
>> that kconfig itself is the right place for this feature.
>>
>> Should this be doable?  Can anyone give me a pointer of what to use,
>> where to begin?
> 
> You can utilize KCONFIG_ALLCONFIG for this:
> $ mv .config config-old
> $ KCONFIG_ALLCONFIG make all<yes|mod|no|rand>config

$ KCONFIG_ALLCONFIG=config-old make all<yes|mod|no|rand>config

of course.

Michal
> 
> The file pointed to by KCONFIG_ALLCONFIG lists options that you wish to
> be set to a given value, see Documentation/kbuild/kconfig.txt.
> 
> Michal
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2010-12-03 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22  4:46 scripted kconfig replies? Randy Dunlap
2010-12-03 13:32 ` Michal Marek
2010-12-03 13:37   ` 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=4CF8F295.6050205@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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