From: patchwork-bot+linux-riscv@kernel.org
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
samuel.holland@sifive.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] riscv: Enable generic CPU vulnerabilites support
Date: Wed, 14 Aug 2024 14:10:36 +0000 [thread overview]
Message-ID: <172364463625.2278280.12786224959163993278.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240703022732.2068316-1-ruanjinjie@huawei.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 3 Jul 2024 10:27:32 +0800 you wrote:
> Currently x86, ARM and ARM64 support generic CPU vulnerabilites, but
> RISC-V not, such as:
>
> # cd /sys/devices/system/cpu/vulnerabilities/
> x86:
> # cat spec_store_bypass
> Mitigation: Speculative Store Bypass disabled via prctl and seccomp
> # cat meltdown
> Not affected
>
> [...]
Here is the summary with links:
- [RFC] riscv: Enable generic CPU vulnerabilites support
https://git.kernel.org/riscv/c/63dd775cc050
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:[~2024-08-14 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 2:27 [RFC PATCH] riscv: Enable generic CPU vulnerabilites support Jinjie Ruan
2024-08-13 17:45 ` Palmer Dabbelt
2024-08-14 14:10 ` 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=172364463625.2278280.12786224959163993278.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ruanjinjie@huawei.com \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
/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