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 <chanwoo@kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: [GIT PULL] devfreq fixes for 5.19-rc6
Date: Fri, 8 Jul 2022 04:41:54 +0900 [thread overview]
Message-ID: <836aec22-fa5c-cbc4-cf9c-0676ea9885a4@gmail.com> (raw)
Dear Rafael,
This is devfreq-fixes pull request for v5.19-rc6. 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 88084a3df1672e131ddc1b4e39eeacfd39864acf:
Linux 5.19-rc5 (2022-07-03 15:39:28 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-fixes-for-5.19-rc6
for you to fetch changes up to c8934e4e348915caac54085c01fd9d04fa16134a:
PM / devfreq: exynos-bus: Fix NULL pointer dereference (2022-07-08 04:32:26 +0900)
----------------------------------------------------------------
Update devfreq for 5.19-rc6
Detailed description for this pull request:
1. Fix NULL pointer error on exynos-bus.c
- Fix exynos-bus NULL pointer dereference by correctly using the local
generated freq_table to output the debug values instead of using the
profile freq_table that is not used in the driver.
----------------------------------------------------------------
Christian Marangi (1):
PM / devfreq: exynos-bus: Fix NULL pointer dereference
drivers/devfreq/exynos-bus.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
reply other threads:[~2022-07-07 19:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=836aec22-fa5c-cbc4-cf9c-0676ea9885a4@gmail.com \
--to=cwchoi00@gmail.com \
--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=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;
as well as URLs for NNTP newsgroup(s).