From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Thomas Renninger <trenn@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] cpupower update for Linux 5.2-rc6
Date: Thu, 27 Jun 2019 23:58:34 +0200 [thread overview]
Message-ID: <4219947.JYe26LCyCL@kreacher> (raw)
In-Reply-To: <376ea5d7-110a-71fe-7b02-efe1b0aed88e@linuxfoundation.org>
On Wednesday, June 12, 2019 10:27:03 PM CEST Shuah Khan wrote:
> This is a multi-part message in MIME format.
> --------------DA1BC82BAC95C219E9AB2661
> Content-Type: text/plain; charset=utf-8; format=flowed
> Content-Transfer-Encoding: 7bit
>
> Hi Rafael,
>
> Please pull the following update for Linux 5.2-rc6 or 5.3 depending on
> your pull request schedule for Linus.
>
> This cpupower update for Linux 5.2-rc6 consists of a fix and a minor
> spelling correction.
>
> diff is attached.
>
> thanks,
> -- Shuah
>
> ----------------------------------------------------------------
> The following changes since commit f2c7c76c5d0a443053e94adb9f0918fa2fb85c3a:
>
> Linux 5.2-rc3 (2019-06-02 13:55:33 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux
> tags/linux-cpupower-5.2-rc6
>
> for you to fetch changes up to 04507c0a9385cc8280f794a36bfff567c8cc1042:
>
> cpupower : frequency-set -r option misses the last cpu in related cpu
> list (2019-06-04 09:06:50 -0600)
Pulled (long ago) and queued for 5.3.
Thanks, and sorry for the delayed response.
prev parent reply other threads:[~2019-06-27 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 20:27 [GIT PULL] cpupower update for Linux 5.2-rc6 Shuah Khan
2019-06-27 21:58 ` Rafael J. Wysocki [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=4219947.JYe26LCyCL@kreacher \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=skhan@linuxfoundation.org \
--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