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 updates for v3.13-rc1
Date: Mon, 25 Nov 2013 17:40:37 +0000 [thread overview]
Message-ID: <20131125174037.GR14725@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]
The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-v3.13-rc1
for you to fetch changes up to 90ba0813db2c96c82e9ba24f30fb96a24a2cd3a8:
Merge remote-tracking branch 'regulator/fix/pfuze100' into regulator-linus (2013-11-24 14:02:50 +0000)
----------------------------------------------------------------
regulator: Fixes for v3.13
A bunch of fixes, a few driver specific ones and a framework fix for
voltage enumeration on fixed voltage regulators which had previously
worked but had been misplaced during some refactoring causing problems
for users that needed to know the voltage.
----------------------------------------------------------------
Charles Keepax (1):
regulator: arizona-micsupp: Correct wm5110 voltage selection
Guennadi Liakhovetski (1):
regulator: fixed: fix regulator_list_voltage() for regression
Laurent Pinchart (1):
regulator: gpio-regulator: Don't oops on missing regulator-type property
Mark Brown (4):
Merge remote-tracking branch 'regulator/fix/arizona' into regulator-linus
Merge remote-tracking branch 'regulator/fix/fixed' into regulator-linus
Merge remote-tracking branch 'regulator/fix/gpio' into regulator-linus
Merge remote-tracking branch 'regulator/fix/pfuze100' into regulator-linus
Tim Harvey (1):
regulator: pfuze100: allow misprogrammed ID
drivers/regulator/arizona-micsupp.c | 54 ++++++++++++++++++++++++++++++++--
drivers/regulator/core.c | 3 ++
drivers/regulator/gpio-regulator.c | 7 ++++-
drivers/regulator/pfuze100-regulator.c | 12 ++++++--
4 files changed, 70 insertions(+), 6 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-11-25 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 17:40 Mark Brown [this message]
2013-11-25 21:10 ` Linus Torvalds
2013-11-26 0:39 ` Mark Brown
2013-11-26 2:50 ` Linus Torvalds
2014-01-21 19:16 ` Linus Torvalds
2014-01-21 20:31 ` Mark Brown
2014-01-23 8:27 ` Takashi Iwai
2014-01-24 0:04 ` H. Peter Anvin
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=20131125174037.GR14725@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®