Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756267AbbBCVJW (ORCPT ); Tue, 3 Feb 2015 16:09:22 -0500 Received: from cantor2.suse.de ([195.135.220.15]:33634 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756172AbbBCVJT (ORCPT ); Tue, 3 Feb 2015 16:09:19 -0500 Date: Wed, 4 Feb 2015 08:09:07 +1100 From: NeilBrown To: Paul Bolle Cc: Jan Beulich , Valentin Rothberg , mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com, james.t.kukunas@linux.intel.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/raid6: correctly check for assembler capabilities Message-ID: <20150204080907.42e43bb4@notabene.brown> In-Reply-To: <1422997415.23894.44.camel@x220> References: <54C2148E02000078000588FB@mail.emea.novell.com> <1422995490.23894.32.camel@x220> <20150204075033.25fb2317@notabene.brown> <1422997415.23894.44.camel@x220> X-Mailer: Claws Mail 3.10.1-162-g4d0ed6 (GTK+ 2.24.25; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/CNiH+TBGCcXNpZ0I4U_f4Ov"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2467 Lines: 63 --Sig_/CNiH+TBGCcXNpZ0I4U_f4Ov Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 03 Feb 2015 22:03:35 +0100 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. > >=20 > > (Well..... I might have made bits of that up, but "git grep 'config AS_= '" > > doesn't find anything). >=20 > 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. >=20 > 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. >=20 Personally, I don't care. But I find that developers in general are more responsive to code than to peeves. So if you post a patch which makes the change that you want, then you are more likely to get a useful response than if you just post a peeve. It may not be the response you want of course.... NeilBrown --Sig_/CNiH+TBGCcXNpZ0I4U_f4Ov Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIVAwUBVNE48znsnt1WYoG5AQIS1hAAs8fuE7GHLgk28bPgn6nBH2JSQi3IxTw7 4/zUvB86V/7HdXkIwZRJ+AXXHb0bHdA3r2bCnB1uDiZBX9cX79CsL6hJ4jTKiWHc 9+hCeaGfZ2grI2j8QWyiWzzqgYuOFLbOWnacqB9K2shdne9lHVN2WGn3MXrdx8rD XkoZCrY5/X3WDVCcbf2GUyJBTuhN84LgvkGoBahmk19F4vRulrKOw/sf2KfNhPLk gqoN3kcS2AUlCerj3vedujyGt0sFPXsHFe9gSYMEQ2tBICNUhWDbxuxs771ifTE/ r5a0irxToYOnsVpka8wFWlcFul/BI7RdiWPdct0YRPPEVBKKjJkx3I6DaXzKgt8j u+y1CcPO70HzBKHS7ypeRz0gPPwNxVyG6Z+jH9Q3QI3DXglHwOUBHG7aOFC5GZl5 O6u/OLdJ79eks3Y+iFYC43MkJlnj1T3oa537IR/YcJq+5iehrMxhnO7tKp2c5y+f a3ZGdb7XVKSeN/RryIW3HGpxvZEhRKIJVlm/qoyoBn/qKw4DVOcK8w2aIUfkzeaE lJkGy+9jtYJ4Cq74dLafbkUOTi7xpbHa9bI5PegJO5Bnxd7PLftRSvWZ9UNJTuok 2GP+SgS8rSewCzdphZMjnn7zHJ24DFoVe81ySpsS2aTlBwOVDmOUivcWVBdVfZq2 DBlMspgU1MI= =rPKZ -----END PGP SIGNATURE----- --Sig_/CNiH+TBGCcXNpZ0I4U_f4Ov-- -- 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/