From: Al Stone <ahs3@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>, ashwin.chaugule@linaro.org
Cc: rjw@rjwysocki.net, lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] Force cppc_cpufreq to report values in KHz to fix user space reporting
Date: Mon, 18 Apr 2016 17:18:58 -0600 [thread overview]
Message-ID: <57156B62.6050405@redhat.com> (raw)
In-Reply-To: <20160418102810.GC2322@vireshk-i7>
On 04/18/2016 04:28 AM, Viresh Kumar wrote:
> Cc'ing Ashwin.
>
Boy, do I feel silly for forgetting that. Thanks, Viresh.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
prev parent reply other threads:[~2016-04-18 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 22:16 [PATCH] Force cppc_cpufreq to report values in KHz to fix user space reporting Al Stone
2016-04-16 5:47 ` kbuild test robot
2016-04-18 10:28 ` Viresh Kumar
2016-04-18 23:18 ` Al Stone [this message]
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=57156B62.6050405@redhat.com \
--to=ahs3@redhat.com \
--cc=ashwin.chaugule@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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).