From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: "Rafael J. Wysocki <rjw@rjwysocki.net>" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chanwoo Choi (samsung.com)" <chanwoo@kernel.org>,
함명주 <myungjoo.ham@samsung.com>
Subject: Re: [GIT PULL] devfreq fixes for v5.6-rc4
Date: Thu, 27 Feb 2020 11:25:54 +0100 [thread overview]
Message-ID: <CAJZ5v0iEpnYG1TZz-kd3cavWU84CGU6Rsk+tsMo5xAh_L1NCPw@mail.gmail.com> (raw)
In-Reply-To: <c9cf6c14-2ff7-6809-2bc7-83ca7974c3b7@samsung.com>
On Thu, Feb 27, 2020 at 5:22 AM Chanwoo Choi <cw00.choi@samsung.com> wrote:
>
> Dear Rafael,
>
> This is devfreq-fixes pull request for v5.6-rc4. I add detailed description of
> this pull request on the following tag. Please pull devfreq with following updates.
> And this patch will be applied to stable tree.
> - tag name : devfreq-fixes-for-5.6-rc4
>
> Best Regards,
> Chanwoo Choi
>
>
> The following changes since commit f8788d86ab28f61f7b46eb6be375f8a726783636:
>
> Linux 5.6-rc3 (2020-02-23 16:17:42 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-fixes-for-5.6-rc4
>
> for you to fetch changes up to 66d0e797bf095d407479c89952d42b1d96ef0a7f:
>
> Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs" (2020-02-24 11:14:29 +0900)
Pulled, thanks!
prev parent reply other threads:[~2020-02-27 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200227042233epcas1p2541b00baa994f262d07c4dc65da99c1c@epcas1p2.samsung.com>
2020-02-27 4:30 ` [GIT PULL] devfreq fixes for v5.6-rc4 Chanwoo Choi
2020-02-27 10:25 ` 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=CAJZ5v0iEpnYG1TZz-kd3cavWU84CGU6Rsk+tsMo5xAh_L1NCPw@mail.gmail.com \
--to=rafael@kernel.org \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.