From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Paul Bolle <pebolle@tiscali.nl>
Cc: Christoph Jaeger <cj@linux.com>,
linux-kernel@vger.kernel.org,
Yalin Wang <yalin.wang@sonymobile.com>,
Will Deacon <will.deacon@arm.com>,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH linux-next] lib: Kconfig: use bool instead of boolean
Date: Mon, 02 Feb 2015 14:53:59 -0800 [thread overview]
Message-ID: <54D00007.4070705@infradead.org> (raw)
In-Reply-To: <20150202144657.c66555dc5bb2b48ccfe0048e@linux-foundation.org>
On 02/02/15 14:46, Andrew Morton wrote:
> On Mon, 02 Feb 2015 23:37:54 +0100 Paul Bolle <pebolle@tiscali.nl> wrote:
>
>> On Mon, 2015-02-02 at 14:27 -0800, Andrew Morton wrote:
>>> There are many uses of "boolean" in lib/Kconfig. Converting just one
>>> of them is inefficient and odd.
>>
>> $ git grep -n "^\s*boolean\b" next-20150202 -- "*Kconfig*"
>> next-20150202:drivers/usb/gadget/Kconfig:427: boolean "USB Webcam function"
>> next-20150202:lib/Kconfig:17: boolean
>>
>> What are Christoph and I missing here?
>
> akpm3:/usr/src/linux-3.19-rc7> grep boolean lib/Kconfig | wc -l
> 15
Those are mostly "corrected" in linux-next or mmotm.
Also, Documentation/kbuild/kconfig-language.txt only uses "bool".
--
~Randy
next prev parent reply other threads:[~2015-02-02 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 14:59 [PATCH linux-next] lib: Kconfig: use bool instead of boolean Christoph Jaeger
2015-02-02 22:27 ` Andrew Morton
2015-02-02 22:37 ` Paul Bolle
2015-02-02 22:46 ` Andrew Morton
2015-02-02 22:52 ` Paul Bolle
2015-02-02 22:53 ` Randy Dunlap [this message]
2015-02-02 22:59 ` Stephen Rothwell
2015-02-02 23:05 ` Russell King - ARM Linux
2015-02-02 23:18 ` Andrew Morton
2015-02-02 23:30 ` Russell King - ARM Linux
2015-02-02 23:40 ` Andrew Morton
2015-02-02 23:12 ` Christoph Jaeger
2015-02-02 23:24 ` Andrew Morton
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=54D00007.4070705@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cj@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=will.deacon@arm.com \
--cc=yalin.wang@sonymobile.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 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.