From: Will Deacon <will@kernel.org>
To: Hanjun Guo <guohanjun@huawei.com>
Cc: Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Pavan Kondeti <pavan.kondeti@oss.qualcomm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] ACPI: GTDT: Correctly number platform devices for MMIO timers
Date: Mon, 1 Dec 2025 13:34:05 +0000 [thread overview]
Message-ID: <aS2ZTfS9YVO98Exe@willie-the-truck> (raw)
In-Reply-To: <71cbdfbc-9281-b0d8-1590-ac666f4f5194@huawei.com>
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
next prev parent reply other threads:[~2025-12-01 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 11:01 Marc Zyngier
2025-11-20 13:58 ` Marc Zyngier
2025-11-21 2:53 ` Hanjun Guo
2025-11-21 8:55 ` Marc Zyngier
2025-11-21 13:14 ` Hanjun Guo
2025-11-27 15:07 ` Will Deacon
2025-11-29 6:02 ` Hanjun Guo
2025-12-01 13:34 ` Will Deacon [this message]
2025-11-24 14:41 ` Will Deacon
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=aS2ZTfS9YVO98Exe@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=guohanjun@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=pavan.kondeti@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
/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®