The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chanwoo Choi <chanwoo@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:DEVICE FREQUENCY (DEVFREQ)" <linux-pm@vger.kernel.org>,
	Chanwoo Choi <chanwoo@kernel.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>
Subject: [GIT PULL] devfreq next for 6.19
Date: Fri, 28 Nov 2025 00:10:42 +0900	[thread overview]
Message-ID: <80e7bf9c-50b3-4e34-aa33-ff9c82479dc9@kernel.org> (raw)

Dear Rafael,

This is devfreq-next pull request. 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 6146a0f1dfae5d37442a9ddcba012add260bceb0:

  Linux 6.18-rc4 (2025-11-02 11:28:02 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-next-for-6.19

for you to fetch changes up to d9600d57668c49308f705a660c5ad17fa3a53f73:

  PM / devfreq: Fix typo in DFSO_DOWNDIFFERENTIAL macro name (2025-11-26 13:58:59 +0900)

----------------------------------------------------------------
Update devfreq next for v6.19

Detailed description for this pull request:
- Move governor.h under include/linux/ and rename to devfreq-governor.h
  in order to allow devfreq governor definitions in out of drivers/devfreq/.

- Fix potential use-after-free issue of OPP handling on hisi_uncore_freq.c

- Use min() to improve the readability on tegra30-devfreq.c

- Fix typo in DFSO_DOWNDIFFERENTIAL macro name on governor_simpleondemand.c
----------------------------------------------------------------

Dmitry Baryshkov (1):
      PM / devfreq: Move governor.h to a public header location

Pengjie Zhang (1):
      PM / devfreq: hisi: Fix potential UAF in OPP handling

Riwen Lu (1):
      PM / devfreq: Fix typo in DFSO_DOWNDIFFERENTIAL macro name

Thorsten Blum (1):
      PM / devfreq: tegra30: use min to simplify actmon_cpu_to_emc_rate

 drivers/devfreq/devfreq.c                          |  2 +-
 drivers/devfreq/governor_passive.c                 | 27 +++++++++++++++++-
 drivers/devfreq/governor_performance.c             |  2 +-
 drivers/devfreq/governor_powersave.c               |  2 +-
 drivers/devfreq/governor_simpleondemand.c          |  6 ++--
 drivers/devfreq/governor_userspace.c               |  2 +-
 drivers/devfreq/hisi_uncore_freq.c                 |  6 ++--
 drivers/devfreq/tegra30-devfreq.c                  | 15 ++++------
 .../governor.h => include/linux/devfreq-governor.h | 33 +++-------------------
 9 files changed, 45 insertions(+), 50 deletions(-)
 rename drivers/devfreq/governor.h => include/linux/devfreq-governor.h (80%)

             reply	other threads:[~2025-11-27 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 15:10 Chanwoo Choi [this message]
2025-11-27 15:30 ` [GIT PULL] devfreq next for 6.19 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=80e7bf9c-50b3-4e34-aa33-ff9c82479dc9@kernel.org \
    --to=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