From: Heiko Stuebner <heiko@sntech.de>
To: palmer@dabbelt.com, paul.walmsley@sifive.com
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
wefu@redhat.com, guoren@kernel.org, mick@ics.forth.gr,
samuel@sholland.org, cmuellner@linux.com,
philipp.tomsich@vrull.eu, hch@lst.de,
Heiko Stuebner <heiko@sntech.de>
Subject: [PATCH 0/4] riscv: some svpbmt fixes
Date: Wed, 18 May 2022 19:02:50 +0200 [thread overview]
Message-ID: <20220518170254.3178923-1-heiko@sntech.de> (raw)
Some additionals comments and notes from autobuilders received
after the series got applied, warranted some changes.
So this is a small collection of cleanups for the svpbmt v10 series.
Heiko Stuebner (4):
riscv: drop cpufeature_apply_feature tracking variable
riscv: Improve description for RISCV_ISA_SVPBMT Kconfig symbol
riscv: make patch-function pointer more generic in
cpu_manufacturer_info struct
riscv: fix dependency for t-head errata
arch/riscv/Kconfig | 9 +++++++--
arch/riscv/Kconfig.erratas | 1 +
arch/riscv/kernel/alternative.c | 18 +++++++++---------
arch/riscv/kernel/cpufeature.c | 5 +----
4 files changed, 18 insertions(+), 15 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-18 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 17:02 Heiko Stuebner [this message]
2022-05-18 17:02 ` [PATCH 1/4] riscv: drop cpufeature_apply_feature tracking variable Heiko Stuebner
2022-05-18 17:02 ` [PATCH 2/4] riscv: Improve description for RISCV_ISA_SVPBMT Kconfig symbol Heiko Stuebner
2022-05-18 17:02 ` [PATCH 3/4] riscv: make patch-function pointer more generic in cpu_manufacturer_info struct Heiko Stuebner
2022-05-18 17:02 ` [PATCH 4/4] riscv: fix dependency for t-head errata Heiko Stuebner
2022-05-20 7:55 ` Guo Ren
2022-05-26 20:58 ` [PATCH 0/4] riscv: some svpbmt fixes Heiko Stübner
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=20220518170254.3178923-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=cmuellner@linux.com \
--cc=guoren@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=samuel@sholland.org \
--cc=wefu@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).