public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: Re: [PATCHv2] kconfig: introduce specialized printer
Date: Fri, 01 Jul 2011 16:51:15 +0200	[thread overview]
Message-ID: <4E0DDEE3.3060207@suse.cz> (raw)
In-Reply-To: <20110609130119.GD4612@sepie.suse.cz>

On 9.6.2011 15:01, Michal Marek wrote:
> On Sun, May 15, 2011 at 11:42:09PM -0400, Arnaud Lacombe wrote:
>> Make conf_write_symbol() grammar agnostic to be able to use it from different
>> code path. These path pass a printer callback which will print a symbol's name
>> and its value in different format.
>>
>> conf_write_symbol()'s job become mostly only to prepare a string for the
>> printer. This avoid to have to pass specialized flag to generic
>> functions
>>
>> Signed-off-by: Arnaud Lacombe<lacombar@gmail.com>
>> ---
>>   scripts/kconfig/confdata.c  |  268 +++++++++++++++++++++++++++----------------
>>   scripts/kconfig/lkc.h       |    5 +
>>   scripts/kconfig/lkc_proto.h |    1 +
>>   scripts/kconfig/symbol.c    |   46 +++++++-
>>   4 files changed, 219 insertions(+), 101 deletions(-)
>>
>> History:
>> v2: Address Michal's comment in msg-id<4D10D7DF.7040903@suse.cz>:
>>   - add brief comment before each printer
>>   - introduce a `skip_unset' variable in kconfig printer
>>   - merge inner switch in an if() statement
>>   - annotate fallthrough
>>   - fix tristate printer behavior
>
> Hi,
>
> below is my merge with current kbuild-2.6.git#kconfig, notably with the
> config_is_xxx() stuff (which we should finalize somehow, but that's not
> the point here). Please review, thanks.
>
>
> Subject: [PATCH] kconfig: introduce specialized printer
>
> Rebase of Arnaud's patch on top of "kconfig: autogenerated config_is_xxx
> macro".

Pushed to kbuild-2.6.git#kconfig.

Michal

  reply	other threads:[~2011-07-01 14:51 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
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 [this message]
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=4E0DDEE3.3060207@suse.cz \
    --to=mmarek@suse.cz \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.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