From: patchwork-bot+linux-riscv@kernel.org
To: Leonardo Bras <leobras@redhat.com>
Cc: linux-riscv@lists.infradead.org, will@kernel.org,
peterz@infradead.org, boqun.feng@gmail.com, mark.rutland@arm.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, guoren@kernel.org, parri.andrea@gmail.com,
geert@linux-m68k.org, mingo@kernel.org, andrzej.hajda@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/5] Rework & improve riscv cmpxchg.h and atomic.h
Date: Wed, 10 Apr 2024 14:20:33 +0000 [thread overview]
Message-ID: <171275883330.18495.10110341843571163280.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240103163203.72768-2-leobras@redhat.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 3 Jan 2024 13:31:58 -0300 you wrote:
> While studying riscv's cmpxchg.h file, I got really interested in
> understanding how RISCV asm implemented the different versions of
> {cmp,}xchg.
>
> When I understood the pattern, it made sense for me to remove the
> duplications and create macros to make it easier to understand what exactly
> changes between the versions: Instruction sufixes & barriers.
>
> [...]
Here is the summary with links:
- [v1,1/5] riscv/cmpxchg: Deduplicate xchg() asm functions
https://git.kernel.org/riscv/c/4bfa185fe3f0
- [v1,2/5] riscv/cmpxchg: Deduplicate cmpxchg() asm and macros
https://git.kernel.org/riscv/c/07a0a41cb77d
- [v1,3/5] riscv/atomic.h : Deduplicate arch_atomic.*
https://git.kernel.org/riscv/c/906123739272
- [v1,4/5] riscv/cmpxchg: Implement cmpxchg for variables of size 1 and 2
https://git.kernel.org/riscv/c/54280ca64626
- [v1,5/5] riscv/cmpxchg: Implement xchg for variables of size 1 and 2
https://git.kernel.org/riscv/c/a8ed2b7a2c13
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-10 14:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 16:31 [PATCH v1 0/5] Rework & improve riscv cmpxchg.h and atomic.h Leonardo Bras
2024-01-03 16:31 ` [PATCH v1 1/5] riscv/cmpxchg: Deduplicate xchg() asm functions Leonardo Bras
2024-01-04 19:53 ` Boqun Feng
2024-01-04 20:41 ` Leonardo Bras
2024-01-04 21:51 ` Boqun Feng
2024-01-05 4:45 ` Leonardo Bras
2024-01-05 5:18 ` Boqun Feng
2024-01-05 6:59 ` Leonardo Bras
2024-01-13 6:54 ` kernel test robot
2024-01-16 19:27 ` Leonardo Bras
2024-01-03 16:32 ` [PATCH v1 2/5] riscv/cmpxchg: Deduplicate cmpxchg() asm and macros Leonardo Bras
2024-01-03 16:32 ` [PATCH v1 3/5] riscv/atomic.h : Deduplicate arch_atomic.* Leonardo Bras
2024-01-03 16:32 ` [PATCH v1 4/5] riscv/cmpxchg: Implement cmpxchg for variables of size 1 and 2 Leonardo Bras
2024-01-03 16:32 ` [PATCH v1 5/5] riscv/cmpxchg: Implement xchg " Leonardo Bras
2024-01-03 16:34 ` [PATCH v1 0/5] Rework & improve riscv cmpxchg.h and atomic.h Leonardo Bras
2024-04-10 14:20 ` patchwork-bot+linux-riscv [this message]
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=171275883330.18495.10110341843571163280.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andrzej.hajda@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=boqun.feng@gmail.com \
--cc=geert@linux-m68k.org \
--cc=guoren@kernel.org \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=palmer@dabbelt.com \
--cc=parri.andrea@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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