From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 50BF82DAFC1; Mon, 1 Dec 2025 13:34:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764596051; cv=none; b=Wco7dT8grhI4rrdJTfTj/exfkTeLtqw7pmdQqR2dVhnOayYUdEJMOtDezYUdfJJ2rwjftn5njP47ZwaHh5LsJxTS0C3gBHn7CHCFY5nx1FVLiGVAkBS12mQkMFB3JSsXrMSpK+jPksqoRTgovDnRUE/M9gshE7hpaIV8eOz/0Jo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764596051; c=relaxed/simple; bh=M6M7eOv7j7NHxq3WPSZpnrzrMCtiltxJ2usZl0W04Io=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=k/O4n5SKw5FuT3QIc9PzwnUzu3QThmzHKG8bENLOoEL5I9hdrnmySgd7YDsS4g+Sot/PiwVJLr2CcqD57AQVHOB4SngZAhO14pzFCF/EB0xddmNn7j0KkGIyRBB969vydV87eTQBt00uPi8NC8DB0brtVYiyiWuBCbuNdnuhYdg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=f5atazrX; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="f5atazrX" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8576BC116D0; Mon, 1 Dec 2025 13:34:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1764596050; bh=M6M7eOv7j7NHxq3WPSZpnrzrMCtiltxJ2usZl0W04Io=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=f5atazrXnzwdIWaicOOKXD2Z54CrOh1WxVE893eX0ZMHoN+tdrLNp5hp5eMuErXU0 Uj6aLYyaIgcTRxMHPjXt5ALYmr0ikeATyI/EQgvBBicftvBQcz5t/tr5Y4UWUR55dE OwoV0lovrohau4HuJcoapCCJXlKoDeZRABVGgeV9mTO3DxFsuHLzwhbEUvQJCF7tBA H6Ejq1qKcOcwZd8Ekg6Me4t5wX19H7W+NEKmEEBgYYo/ke2tajpxfgHx99wqlKoFga N1P4HFnB9PscXtjydKWKsbDfH9bfdfgMlCQDhg5JYUSDiMBckhZ4wk0TpkS8MU3bvL GbPD1mrBjRjFg== Date: Mon, 1 Dec 2025 13:34:05 +0000 From: Will Deacon To: Hanjun Guo Cc: Marc Zyngier , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, Pavan Kondeti , Sudeep Holla , "Rafael J. Wysocki" , Daniel Lezcano , Thomas Gleixner , Mark Rutland , Catalin Marinas Subject: Re: [PATCH] ACPI: GTDT: Correctly number platform devices for MMIO timers Message-ID: References: <20251030110115.1842961-1-maz@kernel.org> <861plrsr1l.wl-maz@kernel.org> <5a742d2a-ac57-f060-913a-6bc9db1e71a2@huawei.com> <71cbdfbc-9281-b0d8-1590-ac666f4f5194@huawei.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: <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