From: Auke Kok <auke-jan.h.kok@intel.com>
To: Thomas Renninger <trenn@suse.de>
Cc: power@bughost.org, cpufreq@vger.kernel.org,
Amit Arora <amit.arora@linaro.org>,
auke@linux.intel.com, amit.kucheria@linaro.org,
yong.shen@linaro.org, vishwanath.bs@ti.com
Subject: Re: [PATCH] Make PowerTOP generic, by removing hard coded values
Date: Wed, 25 Aug 2010 10:13:17 -0700 [thread overview]
Message-ID: <4C754F2D.3000701@intel.com> (raw)
In-Reply-To: <201008251620.09154.trenn@suse.de>
On 08/25/2010 07:20 AM, Thomas Renninger wrote:
> It would also be nice to see libpci getting used instead of
> reimplementing its functionality.
agreed, this might be the elegant way to solve that problem.
Auke
next prev parent reply other threads:[~2010-08-25 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1281684356-7454-1-git-send-email-amit.arora@linaro.org>
[not found] ` <AANLkTimdmQd8m30KuDBMqmXBsjW0zDY9uYpHoXQrJn=L@mail.gmail.com>
2010-08-25 14:20 ` [PATCH] Make PowerTOP generic, by removing hard coded values Thomas Renninger
2010-08-25 17:13 ` Auke Kok [this message]
2010-08-26 5:32 ` Amit Arora
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=4C754F2D.3000701@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=amit.arora@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=auke@linux.intel.com \
--cc=cpufreq@vger.kernel.org \
--cc=power@bughost.org \
--cc=trenn@suse.de \
--cc=vishwanath.bs@ti.com \
--cc=yong.shen@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