public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <chanwoo@kernel.org>
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>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: [GIT PULL] devfreq next for 6.6
Date: Mon, 21 Aug 2023 06:53:23 +0900	[thread overview]
Message-ID: <acaa61be-aa68-22bc-4838-e345de13d2b0@kernel.org> (raw)

Dear Rafael,

This is devfreq-next pull request for v6.6. 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 fdf0eaf11452d72945af31804e2a1048ee1b574c:

  Linux 6.5-rc2 (2023-07-16 15:10:37 -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.6

for you to fetch changes up to 5693d077595de721f9ddbf9d37f40e5409707dfe:

  PM / devfreq: Fix leak in devfreq_dev_release() (2023-08-10 22:48:16 +0900)

----------------------------------------------------------------
Update devfreq next for v6.6

Detailed description for this pull request:
- Include correct DT header including explicitly for imx-bus/imx8m-ddrc/
  mtk-cci/tegra30 tegra drivers.

- Reword the kernel-doc comment for devfreq_monitor_start() API using to specify
the default timer as deferrable timer because devfreq core supports both delayed
timer and deferrable timer according to devfreq device profile.

- Add missing srcu_cleanup_notifier_head() when releasing devfreq device.
: srcu_init_notifier_head() allocates resources that need to be released
with a srcu_cleanup_notifier_head() call.
----------------------------------------------------------------
Boris Brezillon (1):
      PM / devfreq: Fix leak in devfreq_dev_release()

Manivannan Sadhasivam (1):
      PM / devfreq: Reword the kernel-doc comment for devfreq_monitor_start() API

Rob Herring (1):
      PM / devfreq: Explicitly include correct DT includes

 drivers/devfreq/devfreq.c         | 10 ++++++----
 drivers/devfreq/imx-bus.c         |  2 +-
 drivers/devfreq/imx8m-ddrc.c      |  2 +-
 drivers/devfreq/mtk-cci-devfreq.c |  1 -
 drivers/devfreq/tegra30-devfreq.c |  2 +-
 5 files changed, 9 insertions(+), 8 deletions(-)

             reply	other threads:[~2023-08-20 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 21:53 Chanwoo Choi [this message]
2023-08-21 10:56 ` [GIT PULL] devfreq next for 6.6 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=acaa61be-aa68-22bc-4838-e345de13d2b0@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