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.0-rc4
Date: Thu, 08 Sep 2022 13:21:06 +0100	[thread overview]
Message-ID: <20220908122117.93570C433C1@smtp.kernel.org> (raw)

The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:

  Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 475043fabe8c58fb18c32c7942d8754897bd11fa:

  regulator: Fix qcom,spmi-regulator schema (2022-08-31 12:13:17 +0100)

----------------------------------------------------------------
regulator: Fixes for v6.0

One core fix here improving the error handling on enable failure, plus
smaller fixes for the pfuze100 drive and the SPMI DT bindings.

----------------------------------------------------------------
Andrew Halaney (1):
      regulator: core: Clean up on enable failure

Jean-Philippe Brucker (1):
      regulator: Fix qcom,spmi-regulator schema

Xiaolei Wang (1):
      regulator: pfuze100: Fix the global-out-of-bounds access in pfuze100_regulator_probe()

 .../devicetree/bindings/regulator/qcom,spmi-regulator.yaml       | 3 +--
 drivers/regulator/core.c                                         | 9 +++++++--
 drivers/regulator/pfuze100-regulator.c                           | 2 +-
 3 files changed, 9 insertions(+), 5 deletions(-)

             reply	other threads:[~2022-09-08 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 12:21 Mark Brown [this message]
2022-09-08 17:23 ` [GIT PULL] regulator fixes for v6.0-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=20220908122117.93570C433C1@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