From: Paul Bolle <pebolle@tiscali.nl>
To: Christoph Jaeger <cj@linux.com>
Cc: yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, dborkman@redhat.com
Subject: Re: [PATCH 0/3] remove undocumented type definition alias
Date: Mon, 08 Dec 2014 21:20:59 +0100 [thread overview]
Message-ID: <1418070059.2058.39.camel@x220> (raw)
In-Reply-To: <cover.1418003065.git.cj@linux.com>
On Sun, 2014-12-07 at 20:49 -0500, Christoph Jaeger wrote:
> This patchset removes support for the undocumented type definition keyword
> 'boolean', that is used in some config option definitions, in favor of the
> much more widely used 'bool'. Both are semantically equivalent.
>
> % git grep -w bool -- '*Kconfig*' | wc -l
> 7065
> % git grep -w boolean -- '*Kconfig*' | wc -l
> 94
(Side note: I _always_ use: $SOME_GIT_GREP $(git ls-files "*Kconfig*").
Have I been typing too much all those years?)
> Having this alias is more confusing than helpful.
Agree. (boolean is a better keyword than bool. Changing 7065 lines
instead of 94 for that reason alone would be overdoing it.)
> This change was suggested by Daniel Borkmann <dborkman@redhat.com>.
>
>
> Patch 3/3 is purely cosmetic and therefore optional.
>
> Christoph Jaeger (3):
> kconfig: regenerate parser
> kconfig: remove undocumented type definition alias 'boolean'
> kconfig: rename S_BOOLEAN to S_BOOL for consistency
For the record. I tested these three patches, on top of next-20141208,
with this bit of perl:
use 5.016;
use warnings;
use autodie;
exit main ( @ARGV );
sub main {
my ($tree) = @ARGV;
open( my $git_ls_tree, "-|", "git", "ls-tree", "-r", $tree );
my $slurp = do { local $/ = undef; <$git_ls_tree> };
my @lines = split( /\n/, $slurp );
foreach my $line ( @lines ) {
my ( @tmp ) = split( /\s/, $line );
if ($tmp[3] =~ 'defconfig$' ) {
my $arch;
my $defconfig = $tmp[3];
($arch = $tmp[3]) =~ s/arch\/(\w+)\/.*/$1/;
`cp $defconfig .config`;
`yes "" | make ARCH=$arch oldconfig`;
my $out = `md5sum .config`;
my (@tmp) = split( /\s/, $out );
say( $tmp[0] );
}
}
close( $git_ls_tree );
0;
}
Note how I have trouble following my own whitespace rules. If someone
spots a flaw in this approach I'm all ears.
I'll add further feedback on the patches themselves.
Thanks,
Paul Bolle
prev parent reply other threads:[~2014-12-08 20:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 1:49 [PATCH 0/3] remove undocumented type definition alias Christoph Jaeger
2014-12-08 1:49 ` [PATCH 1/3] kconfig: regenerate parser Christoph Jaeger
2014-12-08 20:28 ` Paul Bolle
2014-12-08 1:49 ` [PATCH 2/3] kconfig: remove undocumented type definition alias 'boolean' Christoph Jaeger
2014-12-08 18:51 ` Paul Bolle
2014-12-08 19:13 ` Paul Bolle
2014-12-08 19:16 ` Daniel Borkmann
2014-12-08 19:41 ` Paul Bolle
2014-12-08 20:36 ` Paul Bolle
2014-12-08 21:15 ` Paul Bolle
2014-12-09 11:49 ` Daniel Borkmann
2014-12-09 23:14 ` Christoph Jaeger
2014-12-08 1:49 ` [PATCH 3/3] kconfig: rename S_BOOLEAN to S_BOOL for consistency Christoph Jaeger
2014-12-08 20:43 ` Paul Bolle
2014-12-08 20:20 ` Paul Bolle [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=1418070059.2058.39.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=cj@linux.com \
--cc=dborkman@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yann.morin.1998@free.fr \
/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