From: Catalin Marinas <catalin.marinas@arm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: James Morse <james.morse@arm.com>,
Ben Horgan <ben.horgan@arm.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: MAINTAINERS: Include resctrl MPAM driver
Date: Wed, 18 Feb 2026 17:13:45 +0000 [thread overview]
Message-ID: <aZXzSX7mR6do-xDB@arm.com> (raw)
In-Reply-To: <5e2f98c5-993b-417b-b27c-a683283d1587@oss.qualcomm.com>
On Wed, Feb 18, 2026 at 05:46:40PM +0100, Krzysztof Kozlowski wrote:
> On 18/02/2026 17:23, Catalin Marinas wrote:
> > On Mon, Feb 16, 2026 at 12:02:42PM +0100, Krzysztof Kozlowski wrote:
> >> No maintainers handling the code (so subsystem maintainers) are shown with
> >> scripts/get_maintainers.pl on MPAM drivers in drivers/resctrl/. It
> >> seems that there is no dedicated subsystem for resctrl and existing
> >> drivers went through ARM64 port maintainers, so make that explicit to
> >> avoid patches being lost/ignored.
> >>
> >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> >> ---
> >> MAINTAINERS | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index faa914a5f34d..199058abc152 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -3822,6 +3822,8 @@ S: Maintained
> >> T: git git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> >> F: Documentation/arch/arm64/
> >> F: arch/arm64/
> >> +F: drivers/resctrl/*mpam_*
> >> +F: include/linux/arm_mpam.h
> >> F: drivers/virt/coco/arm-cca-guest/
> >> F: drivers/virt/coco/pkvm-guest/
> >> F: tools/testing/selftests/arm64/
> >
> > What's wrong with the current entry?
>
> I explained in the commit msg:
> "No maintainers handling the code (so subsystem maintainers)"
Yeah, I realised what you meant after sending my reply ;).
> It does not list the maintainers picking up patches, so if you use
> standard tools (like b4, patman or scripted get_maintainers), you will
> never appear on To/Cc list (relying on git-fallback is wrong).
The arm64 maintainers won't proactively pick these patches up unless we
are asked by the MPAM maintainers. I don't mind whether the patches go
in via the arm64 or Greg's drivers tree. We just queued the first drop
as it touched arm64.
Let's see how it goes but I know little about MPAM, so just being on cc
won't make much difference. I rely on the current MPAM maintainers to
tell me what to merge.
Thanks.
--
Catalin
next prev parent reply other threads:[~2026-02-18 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 11:02 [PATCH 1/2] arm_mpam: Force __iomem casts Krzysztof Kozlowski
2026-02-16 11:02 ` [PATCH 2/2] arm64: MAINTAINERS: Include resctrl MPAM driver Krzysztof Kozlowski
2026-02-18 16:23 ` Catalin Marinas
2026-02-18 16:46 ` Krzysztof Kozlowski
2026-02-18 17:13 ` Catalin Marinas [this message]
2026-02-18 17:21 ` Krzysztof Kozlowski
2026-02-27 14:06 ` [PATCH 1/2] arm_mpam: Force __iomem casts Ben Horgan
2026-02-27 14:51 ` Krzysztof Kozlowski
2026-03-06 18:26 ` James Morse
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=aZXzSX7mR6do-xDB@arm.com \
--to=catalin.marinas@arm.com \
--cc=ben.horgan@arm.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.