Message-ID: <55807D28.7090702@zytor.com>
Date: Tue, 16 Jun 2015 12:46:48 -0700
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
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
References: <54C2148E02000078000588FB@mail.emea.novell.com>	 <1422995490.23894.32.camel@x220> <20150204075033.25fb2317@notabene.brown> <1422997415.23894.44.camel@x220>
In-Reply-To: <1422997415.23894.44.camel@x220>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1161
Lines: 29

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/