From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
x86@kernel.org, Al Stone <al.stone@linaro.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Mahesh Sivasubramanian <msivasub@codeaurora.org>,
Ashwin Chaugule <ashwin.chaugule@linaro.org>,
Prashanth Prakash <pprakash@codeaurora.org>
Subject: Re: [PATCH v3 4/5] ACPI / processor_idle : introduce ARCH_SUPPORTS_ACPI_PROCESSOR_CSTATE
Date: Tue, 23 Feb 2016 09:32:14 +0000 [thread overview]
Message-ID: <56CC271E.2020402@arm.com> (raw)
In-Reply-To: <CAJZ5v0jUMcfJw983eJwXExc2Du2Vuycb5A_X+S_QwJzyAysO5g@mail.gmail.com>
On 22/02/16 23:28, Rafael J. Wysocki wrote:
> On Mon, Feb 22, 2016 at 2:46 PM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>> Hi Rafael,
>>
>> On 17/02/16 12:21, Sudeep Holla wrote:
[...]
>>
>> Whatever alternative methods I tried so far ended up much horrible than
>> this. So any suggestions are much appreciated.
>
> Well, you have to give me some time here, sorry.
>
Sorry for the nag.
> I'm still not done with cpufreq at this point and it's going to
> consume some more cycles I'm afraid.
>
I understand, will wait patiently :)
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-02-23 9:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 14:10 [PATCH v3 0/5] ACPI / processor_idle: Add ACPI v6.0 LPI support Sudeep Holla
2015-12-02 14:10 ` [PATCH v3 1/5] ACPI / processor : add support for ACPI0010 processor container Sudeep Holla
2016-02-16 20:10 ` Rafael J. Wysocki
2016-02-17 11:54 ` Sudeep Holla
2016-02-17 11:54 ` [UPDATE] " Sudeep Holla
2016-02-23 23:41 ` Rafael J. Wysocki
2015-12-02 14:10 ` [PATCH v3 2/5] ACPI / sleep: move acpi_processor_sleep to sleep.c Sudeep Holla
2016-02-16 20:13 ` Rafael J. Wysocki
2016-02-17 12:03 ` Sudeep Holla
2016-02-17 12:03 ` [UPDATE] " Sudeep Holla
2016-02-23 23:42 ` Rafael J. Wysocki
2015-12-02 14:10 ` [PATCH v3 3/5] ACPI / processor_idle: replace PREFIX with pr_fmt Sudeep Holla
2016-02-16 20:15 ` Rafael J. Wysocki
2015-12-02 14:10 ` [PATCH v3 4/5] ACPI / processor_idle : introduce ARCH_SUPPORTS_ACPI_PROCESSOR_CSTATE Sudeep Holla
2016-02-16 20:18 ` Rafael J. Wysocki
2016-02-17 12:21 ` Sudeep Holla
2016-02-22 13:46 ` Sudeep Holla
2016-02-22 23:28 ` Rafael J. Wysocki
2016-02-23 9:32 ` Sudeep Holla [this message]
2015-12-02 14:10 ` [PATCH v3 5/5] ACPI / processor_idle: Add support for Low Power Idle(LPI) states Sudeep Holla
2016-02-16 20:46 ` Rafael J. Wysocki
2016-02-17 16:10 ` Sudeep Holla
2016-04-12 4:06 ` Vikas Sajjan
2016-04-12 14:29 ` Sudeep Holla
2015-12-09 22:52 ` [PATCH v3 0/5] ACPI / processor_idle: Add ACPI v6.0 LPI support Prakash, Prashanth
2015-12-10 8:48 ` Sudeep Holla
2016-01-15 19:13 ` Prakash, Prashanth
2016-01-18 12:15 ` Sudeep Holla
2016-01-18 14:53 ` Rafael J. Wysocki
2016-01-27 18:26 ` Sudeep Holla
2016-02-16 20:08 ` Rafael J. Wysocki
2016-02-17 11:37 ` Sudeep Holla
2016-02-18 2:08 ` Rafael J. Wysocki
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=56CC271E.2020402@arm.com \
--to=sudeep.holla@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=al.stone@linaro.org \
--cc=ashwin.chaugule@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msivasub@codeaurora.org \
--cc=pprakash@codeaurora.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=x86@kernel.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).