From: patchwork-bot+linux-riscv@kernel.org
To: Eric Chan <ericchancf@google.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
linux-kernel@vger.kernel.org, conor.dooley@microchip.com,
parri.andrea@gmail.com, emil.renner.berthing@canonical.com,
samuel.holland@sifive.com
Subject: Re: [PATCH v6 0/4] riscv/barrier: tidying up barrier-related macro
Date: Wed, 20 Mar 2024 20:50:39 +0000 [thread overview]
Message-ID: <171096783915.6804.16329473999832420687.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240217131206.3667544-1-ericchancf@google.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sat, 17 Feb 2024 13:12:06 +0000 you wrote:
> This series makes barrier-related macro more neat and clear.
> This is a follow-up to [0-3], change to multiple patches,
> for readability, create new message thread.
>
> v5 -> v6: [PATCH 1/4] let this change to pass review by checkpatch.pl
> instead of overwriting again in [PATCH 4/4]. for [PATCH 4/4] change
> the error message example in commit message to make it more relevant
>
> [...]
Here is the summary with links:
- [v6,1/4] riscv/barrier: Define __{mb,rmb,wmb}
https://git.kernel.org/riscv/c/89f4fd7b1ab7
- [v6,2/4] riscv/barrier: Define RISCV_FULL_BARRIER
https://git.kernel.org/riscv/c/b3c8064ccc44
- [v6,3/4] riscv/barrier: Consolidate fence definitions
https://git.kernel.org/riscv/c/c85688e2b0f0
- [v6,4/4] riscv/barrier: Add missing space after ','
https://git.kernel.org/riscv/c/9133e6e6908d
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-03-20 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 13:12 [PATCH v6 0/4] riscv/barrier: tidying up barrier-related macro Eric Chan
2024-02-17 13:12 ` [PATCH v6 1/4] riscv/barrier: Define __{mb,rmb,wmb} Eric Chan
2024-02-17 13:13 ` [PATCH v6 2/4] riscv/barrier: Define RISCV_FULL_BARRIER Eric Chan
2024-02-17 13:13 ` [PATCH v6 3/4] riscv/barrier: Consolidate fence definitions Eric Chan
2024-02-17 13:13 ` [PATCH v6 4/4] riscv/barrier: Add missing space after ',' Eric Chan
2024-02-19 10:12 ` [PATCH v6 0/4] riscv/barrier: tidying up barrier-related macro Andrea Parri
2024-03-12 4:49 ` Samuel Holland
2024-03-20 20:50 ` 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=171096783915.6804.16329473999832420687.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=emil.renner.berthing@canonical.com \
--cc=ericchancf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=parri.andrea@gmail.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.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