From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-pm@vger.kernel.org
Cc: stewart@linux.vnet.ibm.com, ego@linux.vnet.ibm.com,
rjw@rjwysocki.net, npiggin@gmail.com,
Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
Subject: Re: [v4, 1/2] powernv/cpuidle: Parse dt idle properties into global structure
Date: Wed, 1 Aug 2018 15:23:59 +1000 (AEST) [thread overview]
Message-ID: <41gMDH3hWCz9s3x@ozlabs.org> (raw)
In-Reply-To: <20180705114022.19285-2-akshay.adiga@linux.vnet.ibm.com>
On Thu, 2018-07-05 at 11:40:21 UTC, Akshay Adiga wrote:
> Device-tree parsing happens twice, once while deciding idle state to be
> used for hotplug and once during cpuidle init. Hence, parsing the device
> tree and caching it will reduce code duplication. Parsing code has been
> moved to pnv_parse_cpuidle_dt() from pnv_probe_idle_states(). In addition
> to the properties in the device tree the number of available states is
> also required.
>
> Signed-off-by: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
> Reviewed-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/9c7b185ab2fe313b4426bf55da3624
cheers
next prev parent reply other threads:[~2018-08-01 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 11:40 [PATCH v4 0/2] powernv/cpuidle Device-tree parsing cleanup Akshay Adiga
2018-07-05 11:40 ` [PATCH v4 1/2] powernv/cpuidle: Parse dt idle properties into global structure Akshay Adiga
2018-08-01 5:23 ` Michael Ellerman [this message]
2018-07-05 11:40 ` [PATCH v4 2/2] powernv/cpuidle: Use parsed device tree values for cpuidle_init Akshay Adiga
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=41gMDH3hWCz9s3x@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=stewart@linux.vnet.ibm.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).