[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdWqegF9Akr4N9VwB8bEN+ryMWEybWc7wtcWhMRoHdFYYQ@mail.gmail.com>
Date: Mon, 14 May 2018 23:23:26 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Bart Van Assche <Bart.VanAssche@....com>
Cc: "jcmvbkbc@...il.com" <jcmvbkbc@...il.com>,
"schwidefsky@...ibm.com" <schwidefsky@...ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"deller@....de" <deller@....de>,
"heiko.carstens@...ibm.com" <heiko.carstens@...ibm.com>,
"hch@....de" <hch@....de>,
"fenghua.yu@...el.com" <fenghua.yu@...el.com>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"hpa@...or.com" <hpa@...or.com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will.deacon@....com" <will.deacon@....com>,
"mingo@...hat.com" <mingo@...hat.com>,
"jejb@...isc-linux.org" <jejb@...isc-linux.org>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"chris@...kel.net" <chris@...kel.net>,
"davem@...emloft.net" <davem@...emloft.net>,
"arnd@...db.de" <arnd@...db.de>,
"benh@...nel.crashing.org" <benh@...nel.crashing.org>,
"mpe@...erman.id.au" <mpe@...erman.id.au>,
"paulus@...ba.org" <paulus@...ba.org>
Subject: Re: [PATCH v9 1/2] arch/*: Add CONFIG_ARCH_HAVE_CMPXCHG64
Hi Bart,
On Mon, May 14, 2018 at 10:42 PM, Bart Van Assche
<Bart.VanAssche@....com> wrote:
> On Mon, 2018-05-14 at 11:50 -0700, Max Filippov wrote:
>> On Mon, May 14, 2018 at 11:46 AM, Bart Van Assche
>> <bart.vanassche@....com> wrote:
>> > The next patch in this series introduces a call to cmpxchg64()
>> > in the block layer core for those architectures on which this
>> > functionality is available. Make it possible to test whether
>> > cmpxchg64() is available by introducing CONFIG_ARCH_HAVE_CMPXCHG64.
>> >
>> > ---
>>
>> [...]
>>
>> > diff --git a/arch/xtensa/Kconfig b/arch/xtensa/Kconfig
>> > index c921e8bccdc8..8234278a821d 100644
>> > --- a/arch/xtensa/Kconfig
>> > +++ b/arch/xtensa/Kconfig
>> > @@ -23,6 +23,7 @@ config XTENSA
>> > select HAVE_DMA_CONTIGUOUS
>> > select HAVE_EXIT_THREAD
>> > select HAVE_FUNCTION_TRACER
>> > + select ARCH_HAVE_CMPXCHG64
>>
>> This breaks alphabetical sorting of Kconfig entries.
>
> Hello Max,
>
> Thanks for the feedback. Do you perhaps know whether keeping names in
> alphabetical order is a requirement for arch/xtensa/Kconfig only or
> whether this is required for all arch/*/Kconfig files?
It's a good practice anyway, as it reduces the probability of merge conflicts.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists