linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: add maintainers for arm64 acpi
Date: Tue, 4 Mar 2014 10:23:16 +0000	[thread overview]
Message-ID: <20140304102316.GG30596@arm.com> (raw)
In-Reply-To: <1393899345-7397-2-git-send-email-graeme.gregory@linaro.org>

On Tue, Mar 04, 2014 at 02:15:45AM +0000, Graeme Gregory wrote:
> +ACPI ARM64

That's a pretty broad statement for a single file. Is it core support,
architected peripherals, SoC?

> +M:	Hanjun Guo <hanjun.guo@linaro.org>
> +M:	Graeme Gregory <graeme.gregory@linaro.org>
> +S:	Supported
> +L:	linux-acpi at vger.kernel.org
> +F:	drivers/acpi/plat/arm-core.c

This patch should be part of the series introducing the arm-core.c file
and it will be ACKed (or NAKed) following review. We can't really commit
maintainers to a file which does not exist in mainline and while there is
still feedback to be addressed. It's like a blank cheque.

-- 
Catalin

  parent reply	other threads:[~2014-03-04 10:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  2:15 ARM64 ACPI Maintainers Graeme Gregory
     [not found] ` < 1393899345-7397-2-git-send-email-graeme.gregory@linaro.org>
2014-03-04  2:15 ` [PATCH] MAINTAINERS: add maintainers for arm64 acpi Graeme Gregory
2014-03-04  2:21   ` Joe Perches
2014-03-04  2:28     ` Randy Dunlap
2014-03-04 10:59       ` Grant Likely
2014-03-04 11:15         ` Will Deacon
2014-03-04 17:07           ` Grant Likely
2014-03-04 19:16         ` Graeme Gregory
2014-03-04 23:45         ` Catalin Marinas
2014-03-04 10:23   ` Catalin Marinas [this message]
2014-03-04 19:03     ` Graeme Gregory
2014-03-04 23:50       ` Catalin Marinas
2014-03-07 12:40         ` Grant Likely

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=20140304102316.GG30596@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).