linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: [GIT PULL] regulator fixes for v5.6
Date: Fri, 6 Mar 2020 16:39:06 +0000	[thread overview]
Message-ID: <20200306163906.GD4114@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

The following changes since commit 44e9b3446423164dd04f58a5f9efd988c4d5e84b:

  dt-bindings: regulator: add document bindings for mpq7920 (2020-01-27 17:23:47 +0000)

are available in the Git repository at:

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

for you to fetch changes up to 02fbabd5f4ed182d2c616e49309f5a3efd9ec671:

  regulator: stm32-vrefbuf: fix a possible overshoot when re-enabling (2020-03-04 13:57:28 +0000)

----------------------------------------------------------------
regulator: Fixes for v5.6

A couple of small fixes, one for a minor issue in the stm32-vrefbuf
driver and a documentation fix in the Qualcomm code.

----------------------------------------------------------------
Fabrice Gasnier (1):
      regulator: stm32-vrefbuf: fix a possible overshoot when re-enabling

Petr Vorel (1):
      regulator: qcom_spmi: Fix docs for PM8004

 Documentation/devicetree/bindings/regulator/qcom,spmi-regulator.txt | 2 +-
 drivers/regulator/stm32-vrefbuf.c                                   | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-03-06 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06 16:39 Mark Brown [this message]
2020-03-06 20:55 ` [GIT PULL] regulator fixes for v5.6 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=20200306163906.GD4114@sirena.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).