From: shuah <shuah@kernel.org>
To: Thomas Renninger <trenn@suse.de>,
"Natarajan, Janakarajan" <Janakarajan.Natarajan@amd.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pu Wen <puwen@hygon.com>, Borislav Petkov <bp@suse.de>,
Allison Randal <allison@lohutok.net>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Richard Fontana <rfontana@redhat.com>, shuah <shuah@kernel.org>
Subject: Re: [PATCHv3 0/4] Update cpupower and make it more accurate
Date: Wed, 6 Nov 2019 08:23:54 -0700 [thread overview]
Message-ID: <dee1383b-850c-122b-7466-0b705a213853@kernel.org> (raw)
In-Reply-To: <2247236.ip1NsGyfdn@skinner.arch.suse.de>
On 11/6/19 4:32 AM, Thomas Renninger wrote:
> Thanks Natarajan,
>
> Shuah: I would be ok to queue this up...
>
> Thanks,
>
> Thomas
>
>
>
Thomas,
Already queued up in
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git/log/?h=cpupower
Will send pull request o Rafael today to get these into pm tree.
thanks,
-- Shuah
prev parent reply other threads:[~2019-11-06 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 17:16 Natarajan, Janakarajan
2019-11-05 17:16 ` [PATCHv3 1/4] cpupower: Move needs_root variable into a sub-struct Natarajan, Janakarajan
2019-11-05 17:16 ` [PATCHv3 2/4] cpupower: mperf_monitor: Introduce per_cpu_schedule flag Natarajan, Janakarajan
2019-11-05 17:16 ` [PATCHv3 3/4] cpupower: mperf_monitor: Update cpupower to use the RDPRU instruction Natarajan, Janakarajan
2019-11-05 17:16 ` [PATCHv3 4/4] cpupower: ToDo: Update ToDo with ideas for per_cpu_schedule handling Natarajan, Janakarajan
2019-11-06 11:32 ` [PATCHv3 0/4] Update cpupower and make it more accurate Thomas Renninger
2019-11-06 15:23 ` shuah [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=dee1383b-850c-122b-7466-0b705a213853@kernel.org \
--to=shuah@kernel.org \
--cc=Janakarajan.Natarajan@amd.com \
--cc=allison@lohutok.net \
--cc=bp@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=puwen@hygon.com \
--cc=rfontana@redhat.com \
--cc=tglx@linutronix.de \
--cc=trenn@suse.de \
/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
Powered by JetHome