From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
conor.dooley@microchip.com, paul.walmsley@sifive.com,
zeha@debian.org
Subject: Re: [PATCH] RISC-V: fix taking the text_mutex twice during sifive errata patching
Date: Tue, 07 Mar 2023 21:00:19 +0000 [thread overview]
Message-ID: <167822281950.12297.8704472110602279050.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230302174154.970746-1-conor@kernel.org>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 2 Mar 2023 17:41:55 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Chris pointed out that some bonehead, *cough* me *cough*, added two
> mutex_locks() to the SiFive errata patching. The second was meant to
> have been a mutex_unlock().
>
> Reported-by: Chris Hofstaedtler <zeha@debian.org>
> Fixes: 9493e6f3ce02 ("RISC-V: take text_mutex during alternative patching")
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>
> [...]
Here is the summary with links:
- RISC-V: fix taking the text_mutex twice during sifive errata patching
https://git.kernel.org/riscv/c/bf89b7ee52af
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-03-07 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 17:41 [PATCH] RISC-V: fix taking the text_mutex twice during sifive errata patching Conor Dooley
2023-03-07 20:13 ` Geert Uytterhoeven
2023-03-07 20:17 ` Conor Dooley
2023-03-07 20:38 ` Palmer Dabbelt
2023-03-07 20:52 ` Palmer Dabbelt
2023-03-07 21:00 ` 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=167822281950.12297.8704472110602279050.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=zeha@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.