mirror of https://lore.kernel.org/lkml/
 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.14-rc2
Date: Thu, 13 Feb 2025 19:00:14 +0000	[thread overview]
Message-ID: <e25038550cd571bab188a0e61e2c2b2c.broonie@kernel.org> (raw)

The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:

  Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 35e21de48e693af1dcfdbf2dc3d73dcfa3c8f2d9:

  regulator: core: let dt properties override driver init_data (2025-02-11 16:29:01 +0000)

----------------------------------------------------------------
regulator: Fixes for v6.14

The main change here is a revert for a cleanup that was done in the
core, attempting to resolve some confusion about how we handle systems
where we've somehow managed to end up with both platform data and device
tree data for the same device.  Unfortunately it turns out there are
actually a few systems that deliberately do this and were broken by the
change so we've just reverted it.

There's also a new Qualcomm device ID.

----------------------------------------------------------------
Jerome Brunet (1):
      regulator: core: let dt properties override driver init_data

Varadarajan Narayanan (1):
      regulator: qcom_smd: Add l2, l5 sub-node to mp5496 regulator

 .../bindings/regulator/qcom,smd-rpm-regulator.yaml |  2 +-
 drivers/regulator/core.c                           | 61 ++++++++++------------
 2 files changed, 28 insertions(+), 35 deletions(-)

             reply	other threads:[~2025-02-13 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 19:00 Mark Brown [this message]
2025-02-13 21:30 ` 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=e25038550cd571bab188a0e61e2c2b2c.broonie@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

all inboxes | Powered by JetHome®