From: patchwork-bot+linux-riscv@kernel.org
To: Drew Fustini <fustini@kernel.org>
Cc: linux-riscv@lists.infradead.org, aricciardi@baylibre.com,
alex@ghiti.fr, atishp@rivosinc.com, atish.patra@linux.dev,
babu.moger@amd.com, ben.horgan@arm.com, bp@alien8.de,
cp0613@linux.alibaba.com, conor.dooley@microchip.com,
conor+dt@kernel.org, dave.hansen@linux.intel.com,
Dave.Martin@arm.com, fenghuay@nvidia.com,
gong.shuai@sanechips.com.cn, gsh517@gmail.com,
guo.wenjia23@zte.com.cn, james.morse@arm.com,
mindal@semihalf.com, krzk+dt@kernel.org, liu.qingtao2@zte.com.cn,
zhiwei_liu@linux.alibaba.com, palmer@dabbelt.com, pjw@kernel.org,
peternewman@google.com, rkrcmar@ventanamicro.com,
reinette.chatre@intel.com, robh@kernel.org,
samuel.holland@sifive.com, bigeasy@linutronix.de,
tony.luck@intel.com, vasu@rivosinc.com, ved@rivosinc.com,
liwei1518@gmail.com, cuiyunhui@bytedance.com,
zhangzhanpeng.jasper@bytedance.com, linux-kernel@vger.kernel.org,
x86@kernel.org, devicetree@vger.kernel.org,
linux-rt-devel@lists.linux.dev, linux-doc@vger.kernel.org
Subject: Re: [PATCH v6 0/8] riscv: Add Ssqosid and initial CBQRI resctrl support
Date: Wed, 05 Aug 2026 19:00:04 +0000 [thread overview]
Message-ID: <178595640491.488016.3217391264979488942.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260729-dfustini-atl-sc-cbqri-dt-v6-0-7c22b05d461b@kernel.org>
Hello:
This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:
On Wed, 29 Jul 2026 18:11:27 -0700 you wrote:
> [NOTE: only patches 4 and 8 are different in v6]
>
> This series adds initial RISC-V QoS support: the Ssqosid extension [1]
> (srmcfg CSR), the CBQRI controller interface [2] integrated with resctrl
> [3], and a DT-based platform driver for cache controllers. It has been
> tested on both the Tenstorrent Ascalon Shared Cache controller and a QEMU
> implementation [4].
>
> [...]
Here is the summary with links:
- [v6,1/8] dt-bindings: riscv: Add Ssqosid extension description
(no matching commit)
- [v6,2/8] riscv: Detect the Ssqosid extension
(no matching commit)
- [v6,3/8] riscv: Add support for srmcfg CSR from Ssqosid extension
https://git.kernel.org/riscv/c/3cfa79f25467
- [v6,4/8] riscv_cbqri: Add capacity controller probe and allocation device ops
(no matching commit)
- [v6,5/8] riscv_cbqri: resctrl: Add cache allocation via capacity block mask
(no matching commit)
- [v6,6/8] riscv: Enable resctrl filesystem for Ssqosid
(no matching commit)
- [v6,7/8] dt-bindings: riscv: Add binding for CBQRI controllers
(no matching commit)
- [v6,8/8] riscv_cbqri: Add CBQRI capacity allocation platform driver
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-05 19:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 1:11 [PATCH v6 0/8] riscv: Add Ssqosid and initial CBQRI resctrl support Drew Fustini
2026-07-30 1:11 ` [PATCH v6 1/8] dt-bindings: riscv: Add Ssqosid extension description Drew Fustini
2026-08-05 2:46 ` Paul Walmsley
2026-07-30 1:11 ` [PATCH v6 2/8] riscv: Detect the Ssqosid extension Drew Fustini
2026-08-05 2:47 ` Paul Walmsley
2026-08-05 3:40 ` Drew Fustini
2026-07-30 1:11 ` [PATCH v6 3/8] riscv: Add support for srmcfg CSR from " Drew Fustini
2026-07-30 1:22 ` sashiko-bot
2026-08-05 18:54 ` Paul Walmsley
2026-08-05 20:50 ` Drew Fustini
2026-08-06 1:21 ` Paul Walmsley
2026-07-30 1:11 ` [PATCH v6 4/8] riscv_cbqri: Add capacity controller probe and allocation device ops Drew Fustini
2026-07-30 1:11 ` [PATCH v6 5/8] riscv_cbqri: resctrl: Add cache allocation via capacity block mask Drew Fustini
2026-07-30 1:27 ` sashiko-bot
2026-07-30 1:11 ` [PATCH v6 6/8] riscv: Enable resctrl filesystem for Ssqosid Drew Fustini
2026-07-30 1:11 ` [PATCH v6 7/8] dt-bindings: riscv: Add binding for CBQRI controllers Drew Fustini
2026-07-30 1:11 ` [PATCH v6 8/8] riscv_cbqri: Add CBQRI capacity allocation platform driver Drew Fustini
2026-07-30 1:21 ` sashiko-bot
2026-08-05 3:00 ` [PATCH v6 0/8] riscv: Add Ssqosid and initial CBQRI resctrl support patchwork-bot+linux-riscv
2026-08-05 19:00 ` 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=178595640491.488016.3217391264979488942.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=alex@ghiti.fr \
--cc=aricciardi@baylibre.com \
--cc=atish.patra@linux.dev \
--cc=atishp@rivosinc.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cp0613@linux.alibaba.com \
--cc=cuiyunhui@bytedance.com \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=fenghuay@nvidia.com \
--cc=fustini@kernel.org \
--cc=gong.shuai@sanechips.com.cn \
--cc=gsh517@gmail.com \
--cc=guo.wenjia23@zte.com.cn \
--cc=james.morse@arm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=liu.qingtao2@zte.com.cn \
--cc=liwei1518@gmail.com \
--cc=mindal@semihalf.com \
--cc=palmer@dabbelt.com \
--cc=peternewman@google.com \
--cc=pjw@kernel.org \
--cc=reinette.chatre@intel.com \
--cc=rkrcmar@ventanamicro.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tony.luck@intel.com \
--cc=vasu@rivosinc.com \
--cc=ved@rivosinc.com \
--cc=x86@kernel.org \
--cc=zhangzhanpeng.jasper@bytedance.com \
--cc=zhiwei_liu@linux.alibaba.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