All of lore.kernel.org
 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.5
Date: Mon, 6 Jan 2020 13:06:32 +0000	[thread overview]
Message-ID: <20200106130632.GB6448@sirena.org.uk> (raw)

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

The following changes since commit 62a1923cc8fe095912e6213ed5de27abbf1de77e:

  regulator: rn5t618: fix module aliases (2019-12-16 11:53:37 +0000)

are available in the Git repository at:

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

for you to fetch changes up to 6f1ff76154b8b36033efcbf6453a71a3d28f52cd:

  regulator: bd70528: Remove .set_ramp_delay for bd70528_ldo_ops (2020-01-03 00:58:58 +0000)

----------------------------------------------------------------
regulator: Fixes for v5.5

Three small fixes here, two the result of Axel Lin's amazing work
tracking down inconsistencies in drivers.

----------------------------------------------------------------
Axel Lin (2):
      regulator: axp20x: Fix axp20x_set_ramp_delay
      regulator: bd70528: Remove .set_ramp_delay for bd70528_ldo_ops

Chen-Yu Tsai (1):
      regulator: axp20x: Fix AXP22x ELDO2 regulator enable bitmask

 drivers/regulator/axp20x-regulator.c  | 11 +++++++----
 drivers/regulator/bd70528-regulator.c |  1 -
 2 files changed, 7 insertions(+), 5 deletions(-)

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

             reply	other threads:[~2020-01-06 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 13:06 Mark Brown [this message]
2020-01-06 21:05 ` [GIT PULL] regulator fixes for v5.5 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-12-17 12:33 Mark Brown
2019-12-17 21:15 ` 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=20200106130632.GB6448@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 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.