From: Alexey Klimov <alexey.klimov@arm.com>
To: "Prakash, Prashanth" <pprakash@codeaurora.org>
Cc: linux-acpi@vger.kernel.org, rjw@rjwysocki.net, hotran@apm.com,
cov@codeaurora.org, ashwinch@google.com
Subject: Re: [PATCH V3 0/7] CPPC enhancements
Date: Mon, 12 Sep 2016 12:15:01 +0100 [thread overview]
Message-ID: <20160912111501.GA3875@arm.com> (raw)
In-Reply-To: <321a79e5-00dd-9db6-08c9-7073d656c21a@codeaurora.org>
On Fri, Aug 26, 2016 at 05:43:00PM -0600, Prakash, Prashanth wrote:
> Hi
>
> On 8/16/2016 2:39 PM, Prashanth Prakash wrote:
> > Hi,
> >
> > This series has patches related to cppc that either improves the performance
> > or adds some features.
> Any feedback on this V3 patch set?
>
> Thanks in advance for your inputs.
Hi Prashanth,
I will catch up in next few days.
Best regards,
Alexey
next prev parent reply other threads:[~2016-09-12 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 20:39 [PATCH V3 0/7] CPPC enhancements Prashanth Prakash
2016-08-16 20:39 ` [PATCH V3 1/7] ACPI/CPPC: restructure read/writes for efficient sys mapped reg ops Prashanth Prakash
2016-08-16 20:39 ` [PATCH V3 2/7] ACPI/CPPC: acquire pcc_lock only while accessing PCC subspace Prashanth Prakash
2016-08-16 20:39 ` [PATCH V3 3/7] ACPI/CPPC: support for batching CPPC requests Prashanth Prakash
2016-08-16 20:39 ` [PATCH V3 4/7] ACPI/CPPC: set a non-zero value for transition_latency Prashanth Prakash
2016-08-16 20:39 ` [PATCH V3 5/7] ACPI/CPPC: add sysfs support to compute delivered performance Prashanth Prakash
2016-08-16 20:39 ` [PATCH V3 6/7] ACPI/CPPC: move all PCC related information into pcc_data Prashanth Prakash
2016-08-16 20:39 ` [PATCH V3 7/7] ACPI/CPPC: check for error bit in PCC status field Prashanth Prakash
2016-08-26 23:43 ` [PATCH V3 0/7] CPPC enhancements Prakash, Prashanth
2016-09-12 11:15 ` Alexey Klimov [this message]
2016-09-12 22:07 ` Rafael J. Wysocki
2016-09-14 15:33 ` Prakash, Prashanth
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=20160912111501.GA3875@arm.com \
--to=alexey.klimov@arm.com \
--cc=ashwinch@google.com \
--cc=cov@codeaurora.org \
--cc=hotran@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=pprakash@codeaurora.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.