From: patchwork-bot+linux-riscv@kernel.org
To: Guo Ren <guoren@kernel.org>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, bjorn@rivosinc.com, conor@kernel.org,
leobras@redhat.com, peterz@infradead.org, parri.andrea@gmail.com,
will@kernel.org, longman@redhat.com, boqun.feng@gmail.com,
arnd@arndb.de, alexghiti@rivosinc.com,
linux-kernel@vger.kernel.org, guoren@linux.alibaba.com
Subject: Re: [PATCH] riscv: qspinlock: Fixup _Q_PENDING_LOOPS definition
Date: Thu, 09 Jan 2025 16:16:51 +0000 [thread overview]
Message-ID: <173643941148.1375203.4599909310672567109.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241215135252.201983-1-guoren@kernel.org>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sun, 15 Dec 2024 08:52:52 -0500 you wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> When CONFIG_RISCV_QUEUED_SPINLOCKS=y, the _Q_PENDING_LOOPS
> definition is missing. Add the _Q_PENDING_LOOPS definition for
> pure qspinlock usage.
>
> Fixes: ab83647fadae ("riscv: Add qspinlock support")
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
>
> [...]
Here is the summary with links:
- riscv: qspinlock: Fixup _Q_PENDING_LOOPS definition
https://git.kernel.org/riscv/c/40e6073e7648
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:[~2025-01-09 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 13:52 [PATCH] riscv: qspinlock: Fixup _Q_PENDING_LOOPS definition guoren
2024-12-16 8:23 ` Alexandre Ghiti
2025-01-09 16:16 ` 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=173643941148.1375203.4599909310672567109.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=arnd@arndb.de \
--cc=bjorn@rivosinc.com \
--cc=boqun.feng@gmail.com \
--cc=conor@kernel.org \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=longman@redhat.com \
--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