From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
"Aristeu Rozanski" <aris@redhat.com>,
"Michal Marek" <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
davej@redhat.com, kyle@redhat.com, vgoyal@redhat.com,
arjan@linux.intel.com
Subject: Re: [PATCH] kconfig: introduce nonint_oldconfig and loose_nonint_oldconfig (v3)
Date: Wed, 12 May 2010 14:12:28 +0800 [thread overview]
Message-ID: <20100512061228.GA5718@cr0.nay.redhat.com> (raw)
In-Reply-To: <4BE4237A.8090701@oracle.com>
On Fri, May 07, 2010 at 07:28:10AM -0700, Randy Dunlap wrote:
>On 05/07/10 00:02, Américo Wang wrote:
>> On Thu, May 06, 2010 at 12:48:34PM -0400, Aristeu Rozanski wrote:
>>> This patch has been around for a long time in Fedora and Red Hat Enterprise
>>> Linux kernels and it may be useful for others. The nonint_oldconfig target
>>> will fail and print the unset config options while loose_nonint_oldconfig will
>>> simply let the config option unset. They're useful in distro kernel packages
>>> where the config files are built using a combination of smaller config files.
>>>
>>> Arjan van de Ven wrote the initial nonint_config and Roland McGrath added the
>>> loose_nonint_oldconfig.
>>>
>>> v2:
>>> - when -B and -b are used, return "2" so the reason can be distinguished from
>>> other errors
>>> v3:
>>> - help updated
>>> - nonint_oldconfig won't update the config file if options are missing
>>
>> The patch looks fine, but, why the name 'nonint_oldconfig'?
>> My English is not good enough to see what 'nonint' standards for...
>
>non-interactive
>
Got it, thanks!
next prev parent reply other threads:[~2010-05-12 6:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 19:47 [PATCH] kconfig: introduce nonint_oldconfig and loose_nonint_oldconfig Aristeu Rozanski
2010-04-13 20:00 ` Randy Dunlap
2010-04-13 20:18 ` Aristeu Rozanski
2010-04-13 20:24 ` Randy Dunlap
2010-04-13 20:44 ` Aristeu Rozanski
2010-04-13 21:03 ` [PATCH] kconfig: introduce nonint_oldconfig and loose_nonint_oldconfig (v2) Aristeu Rozanski
2010-04-13 21:26 ` Kyle McMartin
2010-04-14 13:22 ` Michal Marek
2010-05-06 16:48 ` [PATCH] kconfig: introduce nonint_oldconfig and loose_nonint_oldconfig (v3) Aristeu Rozanski
2010-05-07 7:02 ` Américo Wang
2010-05-07 14:28 ` Randy Dunlap
2010-05-12 6:12 ` Américo Wang [this message]
2010-06-02 12:44 ` Michal Marek
2010-04-13 20:43 ` [PATCH] kconfig: introduce nonint_oldconfig and loose_nonint_oldconfig Arjan van de Ven
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=20100512061228.GA5718@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=aris@redhat.com \
--cc=arjan@linux.intel.com \
--cc=davej@redhat.com \
--cc=kyle@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=randy.dunlap@oracle.com \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).