From: patchwork-bot+linux-riscv@kernel.org
To: Evan Green <evan@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, palmer@rivosinc.com,
apatel@ventanamicro.com, aou@eecs.berkeley.edu, heiko@sntech.de,
atishp@rivosinc.com, vineetg@rivosinc.com,
linux-kernel@vger.kernel.org, conor@kernel.org,
conor.dooley@microchip.com, palmer@dabbelt.com,
slewis@rivosinc.com, paul.walmsley@sifive.com,
heiko.stuebner@vrull.eu, ajones@ventanamicro.com
Subject: Re: [PATCH v6 1/6] RISC-V: Move struct riscv_cpuinfo to new header
Date: Wed, 19 Apr 2023 14:30:22 +0000 [thread overview]
Message-ID: <168191462224.22791.2281450562691381145.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230407231103.2622178-2-evan@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 7 Apr 2023 16:10:58 -0700 you wrote:
> In preparation for tracking and exposing microarchitectural details to
> userspace (like whether or not unaligned accesses are fast), move the
> riscv_cpuinfo struct out to its own new cpufeatures.h header. It will
> need to be used by more than just cpu.c.
>
> Signed-off-by: Evan Green <evan@rivosinc.com>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> Reviewed-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
> Tested-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
> Reviewed-by: Paul Walmsley <paul.walmsley@sifive.com>
>
> [...]
Here is the summary with links:
- [v6,1/6] RISC-V: Move struct riscv_cpuinfo to new header
https://git.kernel.org/riscv/c/ff77cf5b2e03
- [v6,2/6] RISC-V: Add a syscall for HW probing
https://git.kernel.org/riscv/c/ea3de9ce8aa2
- [v6,3/6] RISC-V: hwprobe: Add support for RISCV_HWPROBE_BASE_BEHAVIOR_IMA
https://git.kernel.org/riscv/c/00e76e2c6a2b
- [v6,4/6] RISC-V: hwprobe: Support probing of misaligned access performance
https://git.kernel.org/riscv/c/62a31d6e38bd
- [v6,5/6] selftests: Test the new RISC-V hwprobe interface
https://git.kernel.org/riscv/c/287dcc2b0c83
- [v6,6/6] RISC-V: Add hwprobe vDSO function and data
https://git.kernel.org/riscv/c/aa5af0aa90ba
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-04-19 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 23:10 [PATCH v6 0/6] RISC-V Hardware Probing User Interface Evan Green
2023-04-07 23:10 ` [PATCH v6 1/6] RISC-V: Move struct riscv_cpuinfo to new header Evan Green
2023-04-19 14:30 ` patchwork-bot+linux-riscv [this message]
2023-04-07 23:10 ` [PATCH v6 2/6] RISC-V: Add a syscall for HW probing Evan Green
2023-04-07 23:11 ` [PATCH v6 3/6] RISC-V: hwprobe: Add support for RISCV_HWPROBE_BASE_BEHAVIOR_IMA Evan Green
2023-04-14 1:37 ` Paul Walmsley
2023-04-07 23:11 ` [PATCH v6 4/6] RISC-V: hwprobe: Support probing of misaligned access performance Evan Green
2023-04-11 14:06 ` Conor Dooley
2023-04-12 13:50 ` Paul Walmsley
2023-04-07 23:11 ` [PATCH v6 5/6] selftests: Test the new RISC-V hwprobe interface Evan Green
2023-04-07 23:11 ` [PATCH v6 6/6] RISC-V: Add hwprobe vDSO function and data Evan Green
2023-04-11 14:16 ` [PATCH v6 0/6] RISC-V Hardware Probing User Interface Conor Dooley
2023-04-20 17:36 ` Palmer Dabbelt
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=168191462224.22791.2281450562691381145.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=evan@rivosinc.com \
--cc=heiko.stuebner@vrull.eu \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=slewis@rivosinc.com \
--cc=vineetg@rivosinc.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
all inboxes | Powered by JetHome®