From: David Arcari <darcari@redhat.com>
To: Len Brown <lenb@kernel.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/power turbostat: fix output formatting for ACPI CST enumeration
Date: Sat, 22 Aug 2020 08:16:46 -0400 [thread overview]
Message-ID: <d8f50a6a-be68-f92b-e15f-c9f70335643f@redhat.com> (raw)
In-Reply-To: <CAJvTdKms-sO=Qvpnhe4OjE48gXHPzDKbT0i5vK2QuDCxZTt_+Q@mail.gmail.com>
Hi Len,
Thanks for the quick turn around. My apologies for not checking the tree before
sending a follow-up email.
If you decide you prefer to change intel_idle - I'd be happy to do the work if
you'd like. Just let me know.
Thanks,
-Dave
On 8/21/20 2:23 PM, Len Brown wrote:
> Hi Dave,
>
> I think this is fine.
> Indeed, I actually went ahead and applied it a week or so ago.
>
> the only alternative that I can think of is actually shortening the
> ACPI C-state names in the intel_idle driver -- which is still an
> option. It would not be the first time we have tweaked the names used
> in that driver to make tools more happy...
>
> My apology for neglecting to send you an ACK.
> I had intended to send my queued series to the list, which would
> suffice for all the ACKs, but that send and the subsequent push got
> delayed by this and that. So I'll try to ack as I go, so it is clear
> at any time where a patch stands.
>
> thanks!
>
> Len Brown, Intel Open Source Technology Center
>
prev parent reply other threads:[~2020-08-22 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 14:43 [PATCH] tools/power turbostat: fix output formatting for ACPI CST enumeration David Arcari
2020-08-18 13:17 ` David Arcari
2020-08-21 18:23 ` Len Brown
2020-08-22 12:16 ` David Arcari [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=d8f50a6a-be68-f92b-e15f-c9f70335643f@redhat.com \
--to=darcari@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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).