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 fix for v4.7
Date: Tue, 12 Jul 2016 15:51:33 +0100 [thread overview]
Message-ID: <20160712145133.GF9976@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
The following changes since commit 3bfbb4d1a480cc17f6ccfce13b76eb6c0dbeaf8c:
regulator: qcom_smd: add list_voltage callback (2016-06-13 09:51:35 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/qcom-smd-list-voltage
for you to fetch changes up to 43160ffd12c8d1d331362362eea3c70e04b6f9c4:
regulator: qcom_smd: Remove list_voltage callback for rpm_smps_ldo_ops_fixed (2016-06-15 10:18:50 +0100)
----------------------------------------------------------------
regulator: Fix qcom-smd list voltage issues for msm8974
This commit looks like a cleanup but in fact by causing the core to go
down some simplified code paths for noop regulators it avoids a boot
time crash for msm8974 platforms which was introduced in v4.7. It has
been in -next for a while, the issues in mainline for these platforms
weren't flagged up to me until yesterday (I think it took some time to
figure out what was going wrong).
----------------------------------------------------------------
Axel Lin (1):
regulator: qcom_smd: Remove list_voltage callback for rpm_smps_ldo_ops_fixed
drivers/regulator/qcom_smd-regulator.c | 1 -
1 file changed, 1 deletion(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2016-07-12 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 14:51 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-17 18:18 [GIT PULL] regulator fix for v4.7 Mark Brown
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=20160712145133.GF9976@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