All of lore.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.4-rc3
Date: Wed, 24 May 2023 11:12:57 +0100	[thread overview]
Message-ID: <20230524101308.17016C433EF@smtp.kernel.org> (raw)

The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:

  Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)

are available in the Git repository at:

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

for you to fetch changes up to a511637502b1caa135046d0f8fdabd55a31af8ef:

  regulator: mt6359: add read check for PMIC MT6359 (2023-05-18 19:24:47 +0900)

----------------------------------------------------------------
regulator: Fixes for v6.4

Some fixes that came in since the merge window, nothing terribly
exciting - a couple of driver specific fixes and a fix for the error
handling when setting up the debugfs for the devices.

----------------------------------------------------------------
Alexander Stein (1):
      regulator: pca9450: Fix BUCK2 enable_mask

Osama Muhammad (1):
      regulator: Fix error checking for debugfs_create_dir

Sen Chu (1):
      regulator: mt6359: add read check for PMIC MT6359

 drivers/regulator/core.c              | 4 ++--
 drivers/regulator/mt6359-regulator.c  | 7 +++++--
 drivers/regulator/pca9450-regulator.c | 4 ++--
 3 files changed, 9 insertions(+), 6 deletions(-)

             reply	other threads:[~2023-05-24 10:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 10:12 Mark Brown [this message]
2023-05-24 18:48 ` [GIT PULL] regulator fixes for v6.4-rc3 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=20230524101308.17016C433EF@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.