From: Christoph Jaeger <cj@linux.com>
To: yann.morin.1998@free.fr
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
dborkman@redhat.com, Christoph Jaeger <cj@linux.com>
Subject: [PATCH 0/3] remove undocumented type definition alias
Date: Sun, 7 Dec 2014 20:49:17 -0500 [thread overview]
Message-ID: <cover.1418003065.git.cj@linux.com> (raw)
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
Having this alias is more confusing than helpful.
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
arch/cris/arch-v32/drivers/Kconfig | 2 +-
arch/mips/pmcs-msp71xx/Kconfig | 6 +-
drivers/connector/Kconfig | 2 +-
drivers/hwmon/Kconfig | 2 +-
drivers/i2c/Kconfig | 4 +-
drivers/iio/Kconfig | 4 +-
drivers/isdn/hardware/mISDN/Kconfig | 2 +-
drivers/md/Kconfig | 4 +-
drivers/md/persistent-data/Kconfig | 2 +-
drivers/net/ethernet/ti/Kconfig | 4 +-
drivers/net/usb/Kconfig | 12 +-
drivers/net/wireless/rt2x00/Kconfig | 6 +-
drivers/pci/pcie/aer/Kconfig | 2 +-
drivers/rtc/Kconfig | 8 +-
drivers/spi/Kconfig | 6 +-
drivers/staging/board/Kconfig | 2 +-
drivers/staging/emxx_udc/Kconfig | 2 +-
drivers/staging/iio/Kconfig | 4 +-
drivers/tty/serial/Kconfig | 2 +-
drivers/usb/gadget/Kconfig | 26 +-
drivers/usb/gadget/legacy/Kconfig | 2 +-
drivers/usb/gadget/udc/Kconfig | 4 +-
drivers/usb/phy/Kconfig | 2 +-
init/Kconfig | 4 +-
lib/Kconfig | 30 +-
mm/Kconfig | 22 +-
net/Kconfig | 14 +-
net/sched/Kconfig | 2 +-
scripts/kconfig/confdata.c | 22 +-
scripts/kconfig/expr.c | 10 +-
scripts/kconfig/expr.h | 2 +-
scripts/kconfig/gconf.c | 4 +-
scripts/kconfig/mconf.c | 6 +-
scripts/kconfig/menu.c | 10 +-
scripts/kconfig/nconf.c | 4 +-
scripts/kconfig/qconf.cc | 10 +-
scripts/kconfig/symbol.c | 34 +-
scripts/kconfig/zconf.gperf | 5 +-
scripts/kconfig/zconf.hash.c_shipped | 53 +-
scripts/kconfig/zconf.tab.c_shipped | 1248 +++++++++++++++-------------------
scripts/kconfig/zconf.y | 6 +-
security/integrity/Kconfig | 4 +-
security/integrity/evm/Kconfig | 2 +-
43 files changed, 737 insertions(+), 865 deletions(-)
--
2.1.0
next reply other threads:[~2014-12-08 1:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 1:49 Christoph Jaeger [this message]
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 ` [PATCH 0/3] remove undocumented type definition alias Paul Bolle
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=cover.1418003065.git.cj@linux.com \
--to=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