From: Chanwoo Choi <cwchoi00@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "open list:DEVICE FREQUENCY (DEVFREQ)" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: [GIT PULL] devfreq next for 6.1
Date: Mon, 26 Sep 2022 04:31:41 +0900 [thread overview]
Message-ID: <c09e06cf-2461-a3f9-9288-402fbdc94e0d@gmail.com> (raw)
Dear Rafael,
This is devfreq-next pull request for v6.1. I add detailed description of
this pull request on the following tag. Please pull devfreq with
following updates.
Best Regards,
Chanwoo Choi
The following changes since commit 521a547ced6477c54b4b0cc206000406c221b4d6:
Linux 6.0-rc6 (2022-09-18 13:44:14 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-next-for-6.1
for you to fetch changes up to fb2ac84f8acccdec644d26dfc8ba6554f30cd6c0:
PM / devfreq: rockchip-dfi: Fix an error message (2022-09-26 03:59:43 +0900)
----------------------------------------------------------------
Update devfreq next for v6.1
Detailed description for this pull request:
1. Handle -EPROBE_DEFER when regulator is not probed on mtk-ci-devfreq.c
2. Use dev_err_probe to reduce the error log on rockchip-dfi.c
----------------------------------------------------------------
AngeloGioacchino Del Regno (1):
PM / devfreq: mtk-cci: Handle sram regulator probe deferral
Christophe JAILLET (1):
PM / devfreq: rockchip-dfi: Fix an error message
drivers/devfreq/event/rockchip-dfi.c | 7 +++----
drivers/devfreq/mtk-cci-devfreq.c | 8 ++++++--
2 files changed, 9 insertions(+), 6 deletions(-)
next reply other threads:[~2022-09-25 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 19:31 Chanwoo Choi [this message]
2022-09-29 19:24 ` Rafael J. Wysocki
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=c09e06cf-2461-a3f9-9288-402fbdc94e0d@gmail.com \
--to=cwchoi00@gmail.com \
--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=rafael@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
all inboxes | Powered by JetHome®