From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 91DA32BE05F for ; Wed, 18 Feb 2026 17:13:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771434832; cv=none; b=hHkLR2/J+eIZj3TJGYfVsKqEkd7zRXQQXpeIRxWE5l7tOl+gUle8VC1eJUxTH8yDL1LRYy0FPgbtwOmkQGaPlhGD8ZhcYm3ZQ3wrHJkaijqOnSB/n8dgxpYKR0h0eJV5wQeAXsfunJeESz6kh3j6Qt0dr28jVeZ3MsDYS85XDvk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771434832; c=relaxed/simple; bh=FQYPgZDXLlbyzIMTC10LlIMVa6yYnJBLT9IylYCdNGo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=jHr5INYJZSNf2IFVxGks7WRXPrUmTEKyQv8DN6mDo+H6rTAYxyl9LgxA7zGLyMv79trVJUg9Wh6iE7/8MUAAKe+J7x+eXgEpC9LAdtuOLH8fG4Q/19GgIN7Nr55X562leKyvkY9sLudGxqjM/sz+uizNtM9pGUrzENV42Ob/y9M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A35A3339; Wed, 18 Feb 2026 09:13:44 -0800 (PST) Received: from arm.com (arrakis.cambridge.arm.com [10.1.197.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 659753F7F5; Wed, 18 Feb 2026 09:13:49 -0800 (PST) Date: Wed, 18 Feb 2026 17:13:45 +0000 From: Catalin Marinas To: Krzysztof Kozlowski Cc: James Morse , Ben Horgan , Reinette Chatre , Fenghua Yu , Will Deacon , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 2/2] arm64: MAINTAINERS: Include resctrl MPAM driver Message-ID: References: <20260216110240.159691-3-krzysztof.kozlowski@oss.qualcomm.com> <20260216110240.159691-4-krzysztof.kozlowski@oss.qualcomm.com> <5e2f98c5-993b-417b-b27c-a683283d1587@oss.qualcomm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 > >> --- > >> 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