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 v6.3
Date: Wed, 01 Mar 2023 20:34:41 +0000	[thread overview]
Message-ID: <20230301203453.E411FC4339B@smtp.kernel.org> (raw)

The following changes since commit 7f62cb8861190e7cc1018ff37597fc49b2eaafa8:

  regulator: max597x: Align for simple_mfd_i2c driver (2023-02-16 15:54:02 +0000)

are available in the Git repository at:

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

for you to fetch changes up to 80d2c29e09e663761c2778167a625b25ffe01b6f:

  regulator: core: Use ktime_get_boottime() to determine how long a regulator was off (2023-02-23 11:40:14 +0000)

----------------------------------------------------------------
regulator: Fixes for v6.3

Two fixes here, one driver fix for incorrect error codes and a fix in
the core to use ktime_get_boottime() in order to fix accounting of the
time regulators have been powered down over suspend, ktime_get()
pauses over suspend which is not what we want.

----------------------------------------------------------------
Axel Lin (1):
      regulator: max597x: Fix error return code in max597x_get_status

Matthias Kaehlcke (1):
      regulator: core: Use ktime_get_boottime() to determine how long a regulator was off

 drivers/regulator/core.c              | 6 +++---
 drivers/regulator/max597x-regulator.c | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

             reply	other threads:[~2023-03-01 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 20:34 Mark Brown [this message]
2023-03-02 18:34 ` [GIT PULL] regulator fixes for v6.3 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=20230301203453.E411FC4339B@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox