From: Randy Dunlap <rdunlap@infradead.org>
To: Joe Perches <joe@perches.com>,
Graeme Gregory <graeme.gregory@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-acpi@vger.kernel.org, grant.likely@linaro.org,
catalin.marinas@arm.com, will.deacon@arm.com, lenb@kernel.org,
rjw@rjwysocki.net
Subject: Re: [PATCH] MAINTAINERS: add maintainers for arm64 acpi
Date: Mon, 03 Mar 2014 18:28:28 -0800 [thread overview]
Message-ID: <53153A4C.9050602@infradead.org> (raw)
In-Reply-To: <1393899715.20435.8.camel@joe-AO722>
On 03/03/2014 06:21 PM, Joe Perches wrote:
> On Tue, 2014-03-04 at 10:15 +0800, Graeme Gregory wrote:
>> Add maintainers for the arm-core file for arm64 ACPI support
>
> Shouldn't something have to be in the kernel
> tree before there's a MAINTAINERS entry?
or in linux-next and the patch can be added to linux-next (some git tree).
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index c6d0e93..c770d3a 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -259,6 +259,13 @@ F: drivers/pci/*/*acpi*
>> F: drivers/pci/*/*/*acpi*
>> F: tools/power/acpi
>>
>> +ACPI ARM64
>> +M: Hanjun Guo <hanjun.guo@linaro.org>
>> +M: Graeme Gregory <graeme.gregory@linaro.org>
>> +S: Supported
>> +L: linux-acpi@vger.kernel.org
>> +F: drivers/acpi/plat/arm-core.c
>> +
>> ACPI COMPONENT ARCHITECTURE (ACPICA)
>> M: Robert Moore <robert.moore@intel.com>
>> M: Lv Zheng <lv.zheng@intel.com>
--
~Randy
next prev parent reply other threads:[~2014-03-04 2:28 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 [this message]
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
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=53153A4C.9050602@infradead.org \
--to=rdunlap@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=graeme.gregory@linaro.org \
--cc=grant.likely@linaro.org \
--cc=joe@perches.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=will.deacon@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