From: Sasha Levin <sashal@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: stable@vger.kernel.org, conor@kernel.org, palmer@dabbelt.com,
linux@roeck-us.net
Subject: Re: [PATCH 6.1 v2 0/2] RISC-V: fix lock splat in riscv_cpufeature_patch_func()
Date: Fri, 12 May 2023 14:16:37 -0400 [thread overview]
Message-ID: <ZF6CYtsUgA9SFc0p@sashalap> (raw)
In-Reply-To: <20230512-unbroken-preppy-8d726731e8e7@wendy>
On Fri, May 12, 2023 at 08:58:17AM +0100, Conor Dooley wrote:
>Replacing <20230509-suspend-labrador-3eb6f0a8ac77@spud>, here's a more
>complete backport of the patches for the lockdep splats during text
>patching on RISC-V.
>I've preserved the original broken patch & the subsequent fix to it.
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2023-05-12 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 7:58 [PATCH 6.1 v2 0/2] RISC-V: fix lock splat in riscv_cpufeature_patch_func() Conor Dooley
2023-05-12 7:58 ` [PATCH 6.1 v2 1/2] RISC-V: take text_mutex during alternative patching Conor Dooley
2023-05-12 7:58 ` [PATCH 6.1 v2 2/2] RISC-V: fix taking the text_mutex twice during sifive errata patching Conor Dooley
2023-05-12 18:16 ` Sasha Levin [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=ZF6CYtsUgA9SFc0p@sashalap \
--to=sashal@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=linux@roeck-us.net \
--cc=palmer@dabbelt.com \
--cc=stable@vger.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