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 (chanwoo@kernel.org)" <chanwoo@kernel.org>,
함명주 <myungjoo.ham@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>
Subject: Re: [GIT PULL] devfreq next for v5.8
Date: Fri, 29 May 2020 16:42:43 +0200 [thread overview]
Message-ID: <CAJZ5v0jNPH0cCc-mCKMJnNDyC6K29Yw8UOZA2TFMqL8k+eCprg@mail.gmail.com> (raw)
In-Reply-To: <eba2afce-78d0-50ba-8907-da2f61f0df9e@samsung.com>
On Fri, May 29, 2020 at 4:37 AM Chanwoo Choi <cw00.choi@samsung.com> wrote:
>
> Dear Rafael,
>
> This is devfreq-next pull request for v5.8-rc1. I add detailed description of
> this pull request on the following tag. Please pull devfreq with following updates.
> - tag name : devfreq-next-for-5.8
>
> Best Regards,
> Chanwoo Choi
>
>
> The following changes since commit 9cb1fd0efd195590b828b9b865421ad345a4a145:
>
> Linux 5.7-rc7 (2020-05-24 15:32:54 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-next-for-5.8
>
> for you to fetch changes up to 8fc0e48e0faefef5064f3cb803d3d12314e16ec4:
>
> PM / devfreq: Use lockdep asserts instead of manual checks for locked mutex (2020-05-28 18:02:40 +0900)
Pulled, thanks!
prev parent reply other threads:[~2020-05-29 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200529023722epcas1p4062a6826d015c249adddd45bf28c0a29@epcas1p4.samsung.com>
2020-05-29 2:47 ` [GIT PULL] devfreq next for v5.8 Chanwoo Choi
2020-05-29 14:42 ` 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=CAJZ5v0jNPH0cCc-mCKMJnNDyC6K29Yw8UOZA2TFMqL8k+eCprg@mail.gmail.com \
--to=rafael@kernel.org \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@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 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).