From: Thomas Renninger <trenn@suse.de>
To: Jacob Tanenbaum <jtanenba@redhat.com>
Cc: linux-pm@vger.kernel.org, prarit@redhat.com
Subject: Re: [PATCH 0/2] Some changes to "cpupower frequency-info" command
Date: Tue, 10 Nov 2015 17:12:53 +0100 [thread overview]
Message-ID: <2325479.e5jlCo6cZ6@skinner> (raw)
In-Reply-To: <1447097219-31370-1-git-send-email-jtanenba@redhat.com>
On Monday, November 09, 2015 02:26:57 PM Jacob Tanenbaum wrote:
> patch 1:
> - makes every command return a printed message
> - refactors so that debug_output_one uses the functions already in place
> to get the various values to print
This one looks sane. Let me play a bit with it and I add it to my submit queue
if I do not find anything suspicious.
>
> patch 2:
> - fixed bug in how cpuinfo_transition_latency value is interpreted
This is a nice bug fix.
>
> Jacob Tanenbaum (2):
> rework the "cpupower frequency-info" command
> fix how "cpupower frequency-info" interprets latency
Thanks!
Thomas
prev parent reply other threads:[~2015-11-10 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 19:26 [PATCH 0/2] Some changes to "cpupower frequency-info" command Jacob Tanenbaum
2015-11-09 19:26 ` [PATCH 1/2] rework the " Jacob Tanenbaum
2015-11-09 19:26 ` [PATCH 2/2] fix how "cpupower frequency-info" interprets latency Jacob Tanenbaum
2015-11-10 16:12 ` Thomas Renninger [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=2325479.e5jlCo6cZ6@skinner \
--to=trenn@suse.de \
--cc=jtanenba@redhat.com \
--cc=linux-pm@vger.kernel.org \
--cc=prarit@redhat.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