From: James Morse <james.morse@arm.com>
To: Fuad Tabba <fuad.tabba@linux.dev>, Ben Horgan <ben.horgan@arm.com>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Fuad Tabba <tabba@google.com>
Subject: Re: [PATCH] MAINTAINERS: Add mpam.rst to the MPAM DRIVER entry
Date: Fri, 2 Oct 2026 16:28:08 +0100 [thread overview]
Message-ID: <0e78cff6-edd1-4db8-bdb0-7ee6123b146f@arm.com> (raw)
In-Reply-To: <20260903182300.2706684-1-fuad.tabba@linux.dev>
Hi Fuad,
On 03/09/2026 19:23, Fuad Tabba wrote:
> Documentation/arch/arm64/mpam.rst is not listed under MPAM DRIVER, so
> get_maintainer.pl names neither MPAM maintainer on a patch to it.
Fair enough ...
I've picked this up to send on to Catalin...
> Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev>
> ---
>
> Notes:
> Found this while putting together the recipient list for [1]:
> get_maintainer.pl names neither MPAM maintainer on a patch to mpam.rst.
> arch/arm64/kernel/mpam.c, arch/arm64/include/asm/mpam.h and
> drivers/acpi/arm64/mpam.c aren't in this entry either, but that
> didn't look as clear cut, so I've left them out. Happy to respin
> with them added.
I'd leave that - the split is so that stuff in the arm-arm is part of the arch
code, and things that aren't a buried out in drivers.
Thanks,
James
> diff --git a/MAINTAINERS b/MAINTAINERS
> index fc320b373656f..20a6e70df83c8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18438,6 +18438,7 @@ M: Ben Horgan <ben.horgan@arm.com>
> R: Reinette Chatre <reinette.chatre@intel.com>
> R: Fenghua Yu <fenghuay@nvidia.com>
> S: Maintained
> +F: Documentation/arch/arm64/mpam.rst
> F: drivers/resctrl/mpam_*
> F: drivers/resctrl/test_mpam_*
> F: include/linux/arm_mpam.h
prev parent reply other threads:[~2026-10-02 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 18:23 Fuad Tabba
2026-09-07 15:11 ` Ben Horgan
2026-10-02 15:28 ` James Morse [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=0e78cff6-edd1-4db8-bdb0-7ee6123b146f@arm.com \
--to=james.morse@arm.com \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=fuad.tabba@linux.dev \
--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=tabba@google.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 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®