From: patchwork-bot+linux-riscv@kernel.org
To: Andrew Jones <ajones@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, evan@rivosinc.com,
conor.dooley@microchip.com, apatel@ventanamicro.com
Subject: Re: [PATCH v3 0/4] RISC-V: hwprobe: Introduce which-cpus
Date: Fri, 05 Jan 2024 21:50:27 +0000 [thread overview]
Message-ID: <170449142774.26226.5996649817397365731.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231122164700.127954-6-ajones@ventanamicro.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 22 Nov 2023 17:47:01 +0100 you wrote:
> This series introduces a flag for the hwprobe syscall which effectively
> reverses its behavior from getting the values of keys for a set of cpus
> to getting the cpus for a set of key-value pairs.
>
> Change since v2[1]:
> - Rebased on v6.7-rc1 to get green on patchwork (dropped a couple
> patches that were merged with [2])
> - Added an r-b from Conor
>
> [...]
Here is the summary with links:
- [v3,1/4] RISC-V: hwprobe: Clarify cpus size parameter
https://git.kernel.org/riscv/c/36d842d654be
- [v3,2/4] RISC-V: Move the hwprobe syscall to its own file
https://git.kernel.org/riscv/c/53b2b22850e1
- [v3,3/4] RISC-V: hwprobe: Introduce which-cpus flag
https://git.kernel.org/riscv/c/e178bf146e4b
- [v3,4/4] RISC-V: selftests: Add which-cpus hwprobe test
https://git.kernel.org/riscv/c/ef7d6abb2cf5
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-01-05 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 16:47 [PATCH v3 0/4] RISC-V: hwprobe: Introduce which-cpus Andrew Jones
2023-11-22 16:47 ` [PATCH v3 1/4] RISC-V: hwprobe: Clarify cpus size parameter Andrew Jones
2023-11-22 16:47 ` [PATCH v3 2/4] RISC-V: Move the hwprobe syscall to its own file Andrew Jones
2023-11-22 16:47 ` [PATCH v3 3/4] RISC-V: hwprobe: Introduce which-cpus flag Andrew Jones
2023-11-22 19:09 ` Evan Green
2023-11-22 16:47 ` [PATCH v3 4/4] RISC-V: selftests: Add which-cpus hwprobe test Andrew Jones
2024-01-05 21:50 ` 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=170449142774.26226.5996649817397365731.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=conor.dooley@microchip.com \
--cc=evan@rivosinc.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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