mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Catalin Marinas <catalin.marinas@arm.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 18:21:26 +0100	[thread overview]
Message-ID: <ded00e66-3f87-46d5-b41a-a4c9e114e1e1@oss.qualcomm.com> (raw)
In-Reply-To: <aZXzSX7mR6do-xDB@arm.com>

On 18/02/2026 18:13, Catalin Marinas wrote:
> On Wed, Feb 18, 2026 at 05:46:40PM +0100, Krzysztof Kozlowski wrote:
>>>
>>> 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.


OK, there are few subsystems (e.g. cdx) doing something similar -
listing only reviewing maintainer, which later has to poke the actual
maintainer picking up patches. I find it confusing practice and might
lead to patches being lost on the mailing list (happened for example
with cdx...), which is very poor contributor experience, but I
understand you might not want to maintain them (same happened for cdx...).

In that case MPAM folks, please kindly review and pick up only the first
patch. Or tell me what should be done...

Best regards,
Krzysztof

  reply	other threads:[~2026-02-18 17:21 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
2026-02-18 17:21         ` Krzysztof Kozlowski [this message]
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=ded00e66-3f87-46d5-b41a-a4c9e114e1e1@oss.qualcomm.com \
    --to=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=ben.horgan@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=fenghuay@nvidia.com \
    --cc=james.morse@arm.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 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®