From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
"David S . Miller" <davem@davemloft.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v9 1/2] arch/*: Add CONFIG_ARCH_HAVE_CMPXCHG64
Date: Tue, 15 May 2018 10:15:36 +0200 [thread overview]
Message-ID: <20180515081536.GA4901@andrea> (raw)
In-Reply-To: <20180514184634.2160-2-bart.vanassche@wdc.com>
Hi Bart,
On Mon, May 14, 2018 at 11:46:33AM -0700, Bart Van Assche wrote:
[...]
> diff --git a/Documentation/features/locking/cmpxchg64/arch-support.txt b/Documentation/features/locking/cmpxchg64/arch-support.txt
> new file mode 100644
> index 000000000000..65b3290ce5d5
> --- /dev/null
> +++ b/Documentation/features/locking/cmpxchg64/arch-support.txt
> @@ -0,0 +1,31 @@
> +#
> +# Feature name: cmpxchg64
> +# Kconfig: ARCH_HAVE_CMPXCHG64
> +# description: arch supports the cmpxchg64() API
> +#
> + -----------------------
> + | arch |status|
> + -----------------------
> + | alpha: | ok |
> + | arc: | TODO |
> + | arm: |!thumb|
> + | arm64: | ok |
> + | c6x: | TODO |
> + | h8300: | TODO |
> + | hexagon: | TODO |
> + | ia64: | ok |
> + | m68k: | ok |
> + | microblaze: | TODO |
> + | mips: |64-bit|
> + | nios2: | TODO |
> + | openrisc: | TODO |
> + | parisc: | ok |
> + | powerpc: |64-bit|
> + | s390: | ok |
> + | sh: | TODO |
> + | sparc: | ok |
> + | um: | TODO |
> + | unicore32: | TODO |
> + | x86: | ok |
> + | xtensa: | ok |
> + -----------------------
nds32 and riscv seem to be missing from the table. I'd also suggest
sticking to the three entries documented in
Documentation/features/arch-support.txt
and using the header comment to provide any additional information.
A script that refreshes the arch support status file in place (from
the Kconfig files) is currently available in linux-next: c.f.,
Documentation/features/scripts/features-refresh.sh
Andrea
next prev parent reply other threads:[~2018-05-15 8:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 18:46 [PATCH v9 0/2] blk-mq: Rework blk-mq timeout handling again Bart Van Assche
2018-05-14 18:46 ` [PATCH v9 1/2] arch/*: Add CONFIG_ARCH_HAVE_CMPXCHG64 Bart Van Assche
2018-05-14 18:50 ` Max Filippov
2018-05-14 20:42 ` Bart Van Assche
2018-05-14 21:23 ` Geert Uytterhoeven
2018-05-15 2:54 ` Michael Ellerman
2018-05-15 15:14 ` Bart Van Assche
2018-05-15 8:15 ` Andrea Parri [this message]
2018-05-14 18:46 ` [PATCH v9 2/2] blk-mq: Rework blk-mq timeout handling again Bart Van Assche
2018-05-15 13:49 ` Sebastian Ott
-- strict thread matches above, loose matches on Subject: below --
2018-05-15 22:51 [PATCH v10 0/2] " Bart Van Assche
2018-05-15 22:51 ` [PATCH v9 1/2] arch/*: Add CONFIG_ARCH_HAVE_CMPXCHG64 Bart Van Assche
2018-05-16 6:07 ` Christoph Hellwig
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=20180515081536.GA4901@andrea \
--to=andrea.parri@amarulasolutions.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=chris@zankel.net \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=fenghua.yu@intel.com \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=jcmvbkbc@gmail.com \
--cc=jejb@parisc-linux.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).