From: Andrew Morton <akpm@linux-foundation.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Christoph Jaeger <cj@linux.com>,
linux-kernel@vger.kernel.org,
Yalin Wang <yalin.wang@sonymobile.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH linux-next] lib: Kconfig: use bool instead of boolean
Date: Mon, 2 Feb 2015 15:40:20 -0800 [thread overview]
Message-ID: <20150202154020.8af8753afc0386be5b9eab1f@linux-foundation.org> (raw)
In-Reply-To: <20150202233000.GK8656@n2100.arm.linux.org.uk>
On Mon, 2 Feb 2015 23:30:00 +0000 Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> On Mon, Feb 02, 2015 at 03:18:24PM -0800, Andrew Morton wrote:
> > I'm a bit surprised that nobody helped out with the Kconfig text.
> > I queued the below. Looks OK?
> >
> > --- a/lib/Kconfig~a
> > +++ a/lib/Kconfig
> > @@ -18,9 +18,8 @@ config HAVE_ARCH_BITREVERSE
> > default n
> > depends on BITREVERSE
> > help
> > - This option provides an config for the architecture which have instruction
> > - can do bitreverse operation, we use the hardware instruction if the architecture
> > - have this capability.
> > + This option enables the use of hardware bit-reversal instructions on
> > + architectures which support such operations.
>
> Looks fine to me. How are we going to handle this change (and the bool
> bit as well?) Is it something you want me to merge, or will you send
> these changes towards the end of the merge window?
Yep, I can take care of them.
next prev parent reply other threads:[~2015-02-02 23:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 14:59 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
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 [this message]
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=20150202154020.8af8753afc0386be5b9eab1f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cj@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®