public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] regulator fixes for v6.6-rc4
Date: Tue, 03 Oct 2023 19:07:11 +0100	[thread overview]
Message-ID: <20231003180719.2B712C433CA@smtp.kernel.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

The following changes since commit 6223e073db78458f8846c380ccd224a7a73a3867:

  regulator: Fix voltage range selection (2023-09-11 13:51:36 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v6.6-rc4

for you to fetch changes up to 6e800968f6a715c0661716d2ec5e1f56ed9f9c08:

  regulator/core: Revert "fix kobject release warning and memory leak in regulator_register()" (2023-09-26 17:26:08 +0200)

----------------------------------------------------------------
regulator: Fixes for v6.6

Two things here, one is an improved fix for issues around freeing
devices when registration fails which replaces a half baked fix with a
more complete one which uses the device model release() function
properly.  The other fix is a device specific fix for mt6358, the driver
said that the LDOs supported mode configuration but this is not actually
the case and could cause issues.

----------------------------------------------------------------
Chen-Yu Tsai (1):
      regulator: mt6358: split ops for buck and linear range LDO regulators

Michał Mirosław (2):
      regulator/core: regulator_register: set device->class earlier
      regulator/core: Revert "fix kobject release warning and memory leak in regulator_register()"

 drivers/regulator/core.c             | 10 +++-------
 drivers/regulator/mt6358-regulator.c | 18 +++++++++++++++---
 2 files changed, 18 insertions(+), 10 deletions(-)

             reply	other threads:[~2023-10-03 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 18:07 Mark Brown [this message]
2023-10-03 19:32 ` [GIT PULL] regulator fixes for v6.6-rc4 pr-tracker-bot

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=20231003180719.2B712C433CA@smtp.kernel.org \
    --to=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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