From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Kevin Hilman <khilman@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Mark Rutland <Mark.Rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Chander Kashyap <k.chander@samsung.com>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH 1/3] drivers: cpuidle: add status property to ARM idle states
Date: Tue, 21 Oct 2014 17:20:58 +0100 [thread overview]
Message-ID: <20141021162058.GA17610@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <7hbnp6e81x.fsf@deeprootsystems.com>
On Mon, Oct 20, 2014 at 10:38:02PM +0100, Kevin Hilman wrote:
> Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> writes:
>
> > On some platforms the device tree bindings must provide the kernel
> > with a status flag for idle states, that defines whether the idle
> > state is operational or not in the current configuration.
> >
> > This patch adds a status property to the ARM idle states compliant
> > with ePAPR v1.1 and updates the DT parsing code accordingly.
> >
> > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>
> For the series:
>
> Acked-by: Kevin Hilman <khilman@linaro.org>
Thanks ! I will queue it for 3.19 then.
Lorenzo
next prev parent reply other threads:[~2014-10-21 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 13:59 [PATCH 1/3] drivers: cpuidle: add status property to ARM idle states Lorenzo Pieralisi
2014-10-16 13:59 ` [PATCH 2/3] drivers: cpuidle: add idle-state-name description " Lorenzo Pieralisi
2014-10-16 13:59 ` [PATCH 3/3] drivers: cpuidle: remove cpuidle-arm64 duplicate error messages Lorenzo Pieralisi
2014-10-20 21:38 ` [PATCH 1/3] drivers: cpuidle: add status property to ARM idle states Kevin Hilman
2014-10-21 16:20 ` Lorenzo Pieralisi [this message]
[not found] ` <20141021162058.GA17610-7AyDDHkRsp3ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2014-11-10 7:45 ` Daniel Lezcano
2014-11-10 12:48 ` Lorenzo Pieralisi
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=20141021162058.GA17610@e102568-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=k.chander@samsung.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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).