From: Rob Landley <rob@landley.net>
To: Regid Ichira <regid23@nt1.in>
Cc: "Steven Mr. Procrastinator Rostedt" <rostedt@goodmis.org>,
Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README: Alternative configuration commands does not mention make listnewconfig
Date: Thu, 12 Sep 2013 03:18:00 -0500 [thread overview]
Message-ID: <1378973880.1974.11@driftwood> (raw)
In-Reply-To: <20130912003919.GG8821@nt1.in> (from regid23@nt1.in on Wed Sep 11 19:39:19 2013)
On 09/11/2013 07:39:19 PM, Regid Ichira wrote:
> Applied to the tip of linux.git,
> VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0
> Signed-off-by: Regid Ichira <regid23@nt1.in>
> ---
> README | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/README b/README
> index a24ec89..f10c16f 100644
> --- a/README
> +++ b/README
> @@ -228,6 +228,10 @@ CONFIGURING the kernel:
> "make localyesconfig" Similar to localmodconfig, except it will
> convert
> all module options to built in (=y)
> options.
>
> + "make listnewconfig" Based on the contents of your existing
> ./.config
> + file, print all the new config symbols. One
> at a
> + line.
> +
> You can find more information on using the Linux kernel config
> tools
> in Documentation/kbuild/kconfig.txt.
"make help" does, though. Possibly the README should point people at
that instead of trying to keep a (third?) copy of this info in sync?
Rob
next prev parent reply other threads:[~2013-09-12 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 0:39 [PATCH] README: Alternative configuration commands does not mention make listnewconfig Regid Ichira
2013-09-12 1:06 ` Randy Dunlap
2013-09-12 8:18 ` Rob Landley [this message]
2013-09-12 21:26 ` Regid Ichira
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=1378973880.1974.11@driftwood \
--to=rob@landley.net \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=regid23@nt1.in \
--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