From: Johannes Berg <johannes@sipsolutions.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, sam <sam@ravnborg.org>
Subject: Re: [PATCH] introduce HAVE_EFFICIENT_UNALIGNED_ACCESS Kconfig symbol
Date: Tue, 08 Apr 2008 18:00:49 +0200 [thread overview]
Message-ID: <1207670449.5550.6.camel@johannes.berg> (raw)
In-Reply-To: <47FB920F.60503@s5r6.in-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
Stefan,
Thanks for the text review. I'll follow up with a new version in a
minute.
> > --- everything.orig/arch/Kconfig 2008-04-04 23:42:50.000000000 +0200
> > +++ everything/arch/Kconfig 2008-04-04 23:52:15.000000000 +0200
> > @@ -36,3 +36,22 @@ config HAVE_KPROBES
> >
> > config HAVE_KRETPROBES
> > def_bool n
> > +
> > +config HAVE_EFFICIENT_UNALIGNED_ACCESS
> > + def_bool n
> > + help
> > + Some architectures are unable to perform unaligned accesses
> > + without the use of get_unaligned/put_unaligned. Others are
> > + unable to perform such accesses efficiently (e.g. trap on
>
> Wouldn't a comment be more appropriate instead of a help text? This
> option shouldn't be a visible make XYZconfig prompt.
>
> I have no comment on the option itself; it's not my domain.
Note that the help text doesn't mean the option gets to be visible, only
the one-line description does, as in
config XYZ
bool "description"
vs.
config XYZ
bool
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-04-08 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 15:05 [PATCH] introduce HAVE_EFFICIENT_UNALIGNED_ACCESS Kconfig symbol Johannes Berg
2008-04-08 15:41 ` Stefan Richter
2008-04-08 16:00 ` Johannes Berg [this message]
2008-04-08 16:03 ` [PATCH v6] " Johannes Berg
2008-04-08 19:11 ` [PATCH] " Roman Zippel
2008-04-09 13:43 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2008-05-07 21:05 Johannes Berg
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=1207670449.5550.6.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=stefanr@s5r6.in-berlin.de \
/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