From: Ben Hutchings <ben@decadent.org.uk>
To: Michal Marek <mmarek@suse.cz>
Cc: Arnaud Lacombe <lacombar@gmail.com>, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 2/2] [RFC] kconfig/listnewconfig: show default value of new symbel
Date: Wed, 22 Dec 2010 04:44:28 +0000 [thread overview]
Message-ID: <1292993068.2874.31.camel@localhost> (raw)
In-Reply-To: <4D10DA09.6070009@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On Tue, 2010-12-21 at 17:47 +0100, Michal Marek wrote:
> On 5.12.2010 07:35, Arnaud Lacombe wrote:
> > note: I would not mind adding the KCONFIG_VERBOSE logic.
> >
> > Original idea and implementation by Bastian Blank <waldi@debian.org>,
> > Maximilian Attems <max@stro.at> and Ben Hutchings <ben@decadent.org.uk>
> >
> > CC: Ben Hutchings <ben@decadent.org.uk>
> > Signed-off-by: Arnaud Lacombe <lacombar@gmail.com>
> > ---
> > scripts/kconfig/conf.c | 14 +++++++++++++-
> > scripts/kconfig/confdata.c | 4 ++--
> > 2 files changed, 15 insertions(+), 3 deletions(-)
> >
> > diff --git a/scripts/kconfig/conf.c b/scripts/kconfig/conf.c
> > index 5459a38..1b58129 100644
> > --- a/scripts/kconfig/conf.c
> > +++ b/scripts/kconfig/conf.c
> > @@ -411,6 +411,17 @@ conf_childs:
> > indent -= 2;
> > }
> >
> > +
> > +static void
> > +listnewconfig_print_symbol(FILE *fp, struct symbol *sym, const char *val, void *arg)
> > +{
> > + fprintf(fp, "%s%s (default: %s)\n", CONFIG_, sym->name, val);
> > +}
>
> Ben, do you have an opinion on this format versus the standard .config
> produced by your patch?
[...]
The .config format is more useful as it is then possible to copy lines
directly into a .config file. If you're going to apply Arnaud's
preceding patch (1/2) then please let me rewrite mine to apply on top of
that, rather than applying this second patch.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2010-12-22 4:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 6:35 [PATCH 1/2] [RFC] kconfig: introduce specialized printer Arnaud Lacombe
2010-12-05 6:35 ` [PATCH 2/2] [RFC] kconfig/listnewconfig: show default value of new symbel Arnaud Lacombe
2010-12-15 6:28 ` Arnaud Lacombe
2010-12-21 16:47 ` Michal Marek
2010-12-21 17:54 ` Arnaud Lacombe
2010-12-22 4:44 ` Ben Hutchings [this message]
2010-12-22 5:39 ` Arnaud Lacombe
2010-12-15 6:27 ` [PATCH 1/2] [RFC] kconfig: introduce specialized printer Arnaud Lacombe
2010-12-21 16:37 ` Michal Marek
2010-12-21 16:42 ` Arnaud Lacombe
2011-05-16 3:42 ` [PATCHv2] " Arnaud Lacombe
2011-05-31 1:26 ` Arnaud Lacombe
2011-06-08 5:08 ` Arnaud Lacombe
2011-06-09 13:01 ` Michal Marek
2011-07-01 14:51 ` Michal Marek
2011-07-07 1:34 ` Arnaud Lacombe
2011-07-08 17:01 ` Sam Ravnborg
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=1292993068.2874.31.camel@localhost \
--to=ben@decadent.org.uk \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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.