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 v5.10-rc4
Date: Thu, 19 Nov 2020 17:45:08 +0000	[thread overview]
Message-ID: <20201119174529.A5A5921D7A@mail.kernel.org> (raw)

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

The following changes since commit cf1ad559a20d1930aa7b47a52f54e1f8718de301:

  regulator: defer probe when trying to get voltage from unresolved supply (2020-11-03 13:19:01 +0000)

are available in the Git repository at:

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

for you to fetch changes up to 2ba546ebe0ce2af47833d8912ced9b4a579f13cb:

  regulator: ti-abb: Fix array out of bound read access on the first transition (2020-11-18 17:59:24 +0000)

----------------------------------------------------------------
regulator: Fixes for v5.10

Mostly core fixes here, one set from Michał Mirosław which cleans up
some issues introduced as part of the coupled regulators work, one
memory leak during probe and two due to regulators which have an input
supply name and regulator name which are identical, which is very
unusual.  There's also a fix for our handling of the similarly unusual
case where we can't determine if a regulator is enabled during boot.

----------------------------------------------------------------
Michał Mirosław (3):
      regulator: fix memory leak with repeated set_machine_constraints()
      regulator: avoid resolve_supply() infinite recursion
      regulator: workaround self-referent regulators

Nishanth Menon (1):
      regulator: ti-abb: Fix array out of bound read access on the first transition

Pi-Hsun Shih (1):
      regulator: core: don't disable regulator if is_enabled return error.

Sean Nyekjaer (1):
      regulator: pfuze100: limit pfuze-support-disable-sw to pfuze{100,200}

 drivers/regulator/core.c               | 43 ++++++++++++++++++++--------------
 drivers/regulator/pfuze100-regulator.c | 13 ++++++----
 drivers/regulator/ti-abb-regulator.c   | 12 +++++++++-
 3 files changed, 44 insertions(+), 24 deletions(-)

             reply	other threads:[~2020-11-19 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 17:45 Mark Brown [this message]
2020-11-19 19:17 ` [GIT PULL] regulator fixes for v5.10-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=20201119174529.A5A5921D7A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox