From: Thomas Renninger <trenn@suse.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 859978@bugs.debian.org, GSR <gsr.bugs@infernal-iceberg.com>,
linux-pm@vger.kernel.org, Rafael Wysocki <rafael@kernel.org>
Subject: Re: [PATCH] cpupower: Fix turbo frequency reporting for pre-Sandy Bridge cores
Date: Tue, 11 Apr 2017 14:36:17 +0200 [thread overview]
Message-ID: <22617475.I35FT52FBz@skinner> (raw)
In-Reply-To: <20170410232944.GA4152@decadent.org.uk>
Hi Ben,
good catch, thanks!
Could you resubmit adding my Signed-off-by, please.
Rafael could directly pick it up then?
> Reported-by: GSR <gsr.bugs@infernal-iceberg.com>
> Tested-by: GSR <gsr.bugs@infernal-iceberg.com>
These seem not to make much sense, at least not in the kernel changelog?
next prev parent reply other threads:[~2017-04-11 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 23:29 [PATCH] cpupower: Fix turbo frequency reporting for pre-Sandy Bridge cores Ben Hutchings
2017-04-11 12:36 ` Thomas Renninger [this message]
2017-04-11 14:17 ` Ben Hutchings
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=22617475.I35FT52FBz@skinner \
--to=trenn@suse.de \
--cc=859978@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=gsr.bugs@infernal-iceberg.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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).