From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Liam Girwdood <lgirdwood@gmail.com>
Subject: [GIT PULL] regulator fixes for v4.16
Date: Wed, 7 Mar 2018 15:04:31 +0000 [thread overview]
Message-ID: <20180307150431.GI7290@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
The following changes since commit 661e50bc853209e41a5c14a290ca4decc43cbfd1:
Linux 4.16-rc4 (2018-03-04 14:54:11 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v4.16-rc4
for you to fetch changes up to 82a917c59f0e077817c833f537c71b8fd40cbfe1:
Merge remote-tracking branches 'regulator/fix/resume' and 'regulator/fix/stm32-vfrefbuf' into regulator-linus (2018-03-07 14:39:07 +0000)
----------------------------------------------------------------
regulator: Fixes for v4.16
A couple of fixes here:
- Another half of the supend to idle fix from Geert that went in
earlier, both he and I are confused as to why he didn't notice that
this was missing when his earlier fix was merged.
- A simple fix for a test done the wrong way round in the stm32-vrefbuf
driver.
----------------------------------------------------------------
Fabrice Gasnier (1):
regulator: stm32-vrefbuf: fix check on ready flag
Geert Uytterhoeven (1):
regulator: Fix resume from suspend to idle
Mark Brown (1):
Merge remote-tracking branches 'regulator/fix/resume' and 'regulator/fix/stm32-vfrefbuf' into regulator-linus
drivers/regulator/core.c | 2 +-
drivers/regulator/stm32-vrefbuf.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2018-03-07 15:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180307150431.GI7290@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
all inboxes | Powered by JetHome®