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: [RESEND PATCH] riscv: Fixup boot failure when CONFIG_DEBUG_RT_MUTEXES=y
Date: Wed, 11 Dec 2024 22:33:24 +0000 [thread overview]
Message-ID: <173395640424.1729195.252270245008728818.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241130153310.3349484-1-guoren@kernel.org>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sat, 30 Nov 2024 10:33:10 -0500 you wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> When CONFIG_DEBUG_RT_MUTEXES=y, mutex_lock->rt_mutex_try_acquire
> would change from rt_mutex_cmpxchg_acquire to
> rt_mutex_slowtrylock():
> raw_spin_lock_irqsave(&lock->wait_lock, flags);
> ret = __rt_mutex_slowtrylock(lock);
> raw_spin_unlock_irqrestore(&lock->wait_lock, flags);
>
> [...]
Here is the summary with links:
- [RESEND] riscv: Fixup boot failure when CONFIG_DEBUG_RT_MUTEXES=y
https://git.kernel.org/riscv/c/b3134b8c1a1c
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-12-11 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 15:33 [RESEND PATCH] riscv: Fixup boot failure when CONFIG_DEBUG_RT_MUTEXES=y guoren
2024-12-02 11:22 ` Conor Dooley
2024-12-04 8:27 ` Alexandre Ghiti
2024-12-04 9:10 ` Guo Ren
2024-12-11 21:59 ` Palmer Dabbelt
2024-12-08 0:35 ` Nam Cao
2024-12-11 22:33 ` 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=173395640424.1729195.252270245008728818.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