From: Will Deacon <will.deacon@arm.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org, Hanjun Guo <hanjun.guo@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: Add LAKML list to ACPI for ARM64 entry
Date: Mon, 14 Jan 2019 17:36:17 +0000 [thread overview]
Message-ID: <20190114173617.GA26808@fuggles.cambridge.arm.com> (raw)
In-Reply-To: <20190111120419.10775-1-lorenzo.pieralisi@arm.com>
On Fri, Jan 11, 2019 at 12:04:19PM +0000, Lorenzo Pieralisi wrote:
> Patches for ACPI for ARM64 must be posted and reviewed on the Linux
> ARM kernel mailing list (in addition to linux-acpi@vger) since they
> affect (and are merged through) the ARM64 tree.
>
> Make this explicit.
>
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Hanjun Guo <hanjun.guo@linaro.org>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 32d444476a90..442ec4db7342 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -365,6 +365,7 @@ M: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> M: Hanjun Guo <hanjun.guo@linaro.org>
> M: Sudeep Holla <sudeep.holla@arm.com>
> L: linux-acpi@vger.kernel.org
> +L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> S: Maintained
> F: drivers/acpi/arm64
Makes sense:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2019-01-14 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 12:04 [PATCH] MAINTAINERS: Add LAKML list to ACPI for ARM64 entry Lorenzo Pieralisi
2019-01-12 3:08 ` Hanjun Guo
2019-01-14 17:36 ` Will Deacon [this message]
2019-01-21 17:57 ` Catalin Marinas
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=20190114173617.GA26808@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=hanjun.guo@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).