From: "H. Peter Anvin" <hpa@zytor.com>
To: Paul Bolle <pebolle@tiscali.nl>, NeilBrown <neilb@suse.de>
Cc: Jan Beulich <JBeulich@suse.com>,
Valentin Rothberg <valentinrothberg@gmail.com>,
mingo@elte.hu, tglx@linutronix.de,
james.t.kukunas@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/raid6: correctly check for assembler capabilities
Date: Tue, 16 Jun 2015 12:46:48 -0700 [thread overview]
Message-ID: <55807D28.7090702@zytor.com> (raw)
In-Reply-To: <1422997415.23894.44.camel@x220>
On 02/03/2015 01:03 PM, Paul Bolle wrote:
> On Wed, 2015-02-04 at 07:50 +1100, NeilBrown wrote:
>> Actually the prefix of this macro is "CONFIG_AS_", not "CONFIG_" :-)
>> CONFIG_AS_ is reserved for assembly magic, and is never used by the the
>> kconfig system.
>>
>> (Well..... I might have made bits of that up, but "git grep 'config AS_'"
>> doesn't find anything).
>
> That's correct, there are no Kconfig symbols starting with AS_. But
> still, I would like to hear whether there's a reasonable chance I might
> convince other people to adopt my peeve.
>
> The thinking behind that peeve is, basically, that where people
> encounter a CONFIG_* macro they should only have to check the .config
> file to see how that macro was evaluated in the build that was used.
>
There is a hope/intent that eventually the config system will be able to
incorporate toolchain dependencies for a bunch of reasons.
-hpa
next prev parent reply other threads:[~2015-06-16 19:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 8:29 [PATCH] x86/raid6: correctly check for assembler capabilities Jan Beulich
2015-01-23 16:16 ` Thomas Gleixner
2015-01-28 5:02 ` NeilBrown
2015-02-03 20:31 ` Paul Bolle
2015-02-03 20:50 ` NeilBrown
2015-02-03 21:03 ` Paul Bolle
2015-02-03 21:09 ` NeilBrown
2015-02-03 21:24 ` Valentin Rothberg
2015-02-04 7:51 ` Jan Beulich
2015-06-16 19:46 ` H. Peter Anvin [this message]
2015-06-16 19:56 ` Paul Bolle
2015-06-16 20:05 ` H. Peter Anvin
2015-06-16 20:37 ` Paul Bolle
2015-06-16 20:42 ` H. Peter Anvin
2015-06-16 20:51 ` 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=55807D28.7090702@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=james.t.kukunas@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
--cc=pebolle@tiscali.nl \
--cc=tglx@linutronix.de \
--cc=valentinrothberg@gmail.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