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 v5.9-rc4
Date: Fri, 11 Sep 2020 13:22:23 +0100	[thread overview]
Message-ID: <20200911122317.2E34421D40@mail.kernel.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2134 bytes --]

The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:

  Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 59ae97a7a9e1499c2070e29841d1c4be4ae2994a:

  regulator: pwm: Fix machine constraints application (2020-09-02 19:13:29 +0100)

----------------------------------------------------------------
regulator: Fixes for v5.9

The biggest set of fixes here is those from Michał Mirosław fixing some
locking issues with coupled regulators that are triggered in cases where
a coupled regulator is used by a device involved in fs_reclaim like eMMC
storage.  These are relatively serious for the affected systems, though
the circumstances where they trigger are very rare.

----------------------------------------------------------------
Axel Lin (1):
      regulator: cros-ec-regulator: Add NULL test for devm_kmemdup call

Colin Ian King (1):
      regulator: fix spelling mistake "Cant" -> "Can't"

Dmitry Osipenko (1):
      regulator: core: Fix slab-out-of-bounds in regulator_unlock_recursive()

Mark Brown (1):
      Merge tag 'v5.9-rc2' into regulator-5.9

Michał Mirosław (7):
      regulator: push allocation in regulator_init_coupling() outside of lock
      regulator: push allocation in regulator_ena_gpio_request() out of lock
      regulator: push allocations in create_regulator() outside of lock
      regulator: push allocation in set_consumer_device_supply() out of lock
      regulator: plug of_node leak in regulator_register()'s error path
      regulator: cleanup regulator_ena_gpio_free()
      regulator: remove superfluous lock in regulator_resolve_coupling()

Vincent Whitchurch (1):
      regulator: pwm: Fix machine constraints application

 drivers/regulator/core.c              | 179 ++++++++++++++++++----------------
 drivers/regulator/cros-ec-regulator.c |   3 +
 drivers/regulator/fixed.c             |   2 +-
 drivers/regulator/pwm-regulator.c     |   2 +-
 4 files changed, 101 insertions(+), 85 deletions(-)

             reply	other threads:[~2020-09-11 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 12:22 Mark Brown [this message]
2020-09-11 18:37 ` [GIT PULL] regulator fixes for v5.9-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=20200911122317.2E34421D40@mail.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.