All of lore.kernel.org
 help / color / mirror / Atom feed
From: chenlifu <chenlifu@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 -next] scripts: add compare-config utility
Date: Wed, 13 Apr 2022 17:23:07 +0800	[thread overview]
Message-ID: <ddb5b0f5-bdfd-9a8e-cc58-e4bb73813b80@huawei.com> (raw)
In-Reply-To: <1dd4c336-d281-6da3-ba37-d13bbf7c2537@infradead.org>



在 2022/4/13 0:51, Randy Dunlap 写道:
> Hi--
> 
> On 4/12/22 01:30, Chen Lifu wrote:
>> This is an alternative utility to compare two .config files. Unlike
>> existing utilities "diffconfig" in the kernel tree, it prints detailed
>> results in table style, and support config name prefix so that it can be
>> used elsewhere. It is useful sometimes, for example, to analyze .config files
>> through tables, or to compare Buildroot .config.
>>
>> With grep and awk, it can print similar results like "diffconfg" as well.
>>
>> Signed-off-by: Chen Lifu <chenlifu@huawei.com>
> 
> Is your goal to have this merged into the kernel source tree?
> If so, you should also send the patch the the kconfig maintainer and
> mailing list.
> 
> The output is quite verbose in its default mode (no options specified).
> To get something useful, I use -C -O -N.
> 
> For my uses and preferences, I would like to see a -D (e.g.) which
> is just a combination of -CON. And it would be nice if that was the
> default mode also. :)
> 
>> ---
>> Changes in v2:
>> - Add config name prefix support
>>
>>   scripts/compare-config | 201 +++++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 201 insertions(+)
>>   create mode 100755 scripts/compare-config
> 
> thanks.
> 

Hi, Randy,
Thanks for your friendly comment, I will add -D option and set it as 
default mode.

Chen Lifu

      reply	other threads:[~2022-04-13  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  8:30 [PATCH v2 -next] scripts: add compare-config utility Chen Lifu
2022-04-12 16:51 ` Randy Dunlap
2022-04-13  9:23   ` chenlifu [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=ddb5b0f5-bdfd-9a8e-cc58-e4bb73813b80@huawei.com \
    --to=chenlifu@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 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.