From: Catalin Marinas <catalin.marinas@arm.com>
To: Graeme Gregory <graeme@xora.org.uk>
Cc: "graeme.gregory@linaro.org" <graeme.gregory@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"lenb@kernel.org" <lenb@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: add maintainers for arm64 acpi
Date: Tue, 4 Mar 2014 23:50:44 +0000 [thread overview]
Message-ID: <20140304235044.GB11418@arm.com> (raw)
In-Reply-To: <20140304190318.GE28736@xora-yoga13>
On Tue, Mar 04, 2014 at 07:03:18PM +0000, Graeme Gregory wrote:
> On Tue, Mar 04, 2014 at 10:23:16AM +0000, Catalin Marinas wrote:
> > 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?
> >
> Hi Catalin would changing the title to ACPI ARM64 Core Support be better
> in your mind. I do intend for the maintainership to cover just the
> plat/arm-core.c file.
See my reply to Grant. If that's the only thing you guys are aiming for,
who's in charge of the other bits? Face-to-face meeting in 3 hours
anyway, so we can get back here with the conclusion.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
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 23:50:44 +0000 [thread overview]
Message-ID: <20140304235044.GB11418@arm.com> (raw)
In-Reply-To: <20140304190318.GE28736@xora-yoga13>
On Tue, Mar 04, 2014 at 07:03:18PM +0000, Graeme Gregory wrote:
> On Tue, Mar 04, 2014 at 10:23:16AM +0000, Catalin Marinas wrote:
> > 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?
> >
> Hi Catalin would changing the title to ACPI ARM64 Core Support be better
> in your mind. I do intend for the maintainership to cover just the
> plat/arm-core.c file.
See my reply to Grant. If that's the only thing you guys are aiming for,
who's in charge of the other bits? Face-to-face meeting in 3 hours
anyway, so we can get back here with the conclusion.
--
Catalin
next prev parent reply other threads:[~2014-03-04 23:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 2:15 ARM64 ACPI Maintainers Graeme Gregory
2014-03-04 2:15 ` 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:15 ` Graeme Gregory
2014-03-04 2:21 ` Joe Perches
2014-03-04 2:21 ` Joe Perches
2014-03-04 2:28 ` Randy Dunlap
2014-03-04 2:28 ` Randy Dunlap
2014-03-04 2:28 ` Randy Dunlap
2014-03-04 10:59 ` Grant Likely
2014-03-04 10:59 ` Grant Likely
2014-03-04 11:15 ` Will Deacon
2014-03-04 11:15 ` Will Deacon
2014-03-04 17:07 ` Grant Likely
2014-03-04 17:07 ` Grant Likely
2014-03-04 19:16 ` Graeme Gregory
2014-03-04 19:16 ` Graeme Gregory
2014-03-04 23:45 ` Catalin Marinas
2014-03-04 23:45 ` Catalin Marinas
2014-03-04 10:23 ` Catalin Marinas
2014-03-04 10:23 ` Catalin Marinas
2014-03-04 19:03 ` Graeme Gregory
2014-03-04 19:03 ` Graeme Gregory
2014-03-04 23:50 ` Catalin Marinas [this message]
2014-03-04 23:50 ` Catalin Marinas
2014-03-07 12:40 ` Grant Likely
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=20140304235044.GB11418@arm.com \
--to=catalin.marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=graeme.gregory@linaro.org \
--cc=graeme@xora.org.uk \
--cc=grant.likely@linaro.org \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.