[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aS2ZTfS9YVO98Exe@willie-the-truck>
Date: Mon, 1 Dec 2025 13:34:05 +0000
From: Will Deacon <will@...nel.org>
To: Hanjun Guo <guohanjun@...wei.com>
Cc: Marc Zyngier <maz@...nel.org>, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org,
Pavan Kondeti <pavan.kondeti@....qualcomm.com>,
Sudeep Holla <sudeep.holla@....com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Mark Rutland <mark.rutland@....com>,
Catalin Marinas <catalin.marinas@....com>
Subject: Re: [PATCH] ACPI: GTDT: Correctly number platform devices for MMIO
timers
On Sat, Nov 29, 2025 at 02:02:34PM +0800, Hanjun Guo wrote:
> On 2025/11/27 23:07, Will Deacon wrote:
> > Catalin and I were chatting the other day and we wondered whether it's
> > worth adding something to MAINTAINERS so that we get CC'd on arm64 ACPI
> > patches without you having to add us in manually? We wouldn't merge
> > anything without an Ack from somebody listed under the "ACPI FOR ARM64"
> > entry but it would mean that we get picked up by get_maintainer.pl.
> >
> > What do you think?
>
> Looks great to me!
>
> >
> > I can't tell whether this would be best as an F: line under the arm64
> > architecture entry, or adding us as R:/M: for the ACPI/arm64 entry.
>
> How about adding M: for the ACPI/arm64 entry? I can send a patch
> for this change if you and Catalin agree with it.
Sure, that's fine by me. We'll still want Acks from the currently listed
folks when merging patches, though, so we're not letting you off the
hook that easily :p
Will
Powered by blists - more mailing lists