From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Liam Girdwood <Liam.R.Girdwood@intel.com>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] regulator updates for v3.8
Date: Wed, 6 Feb 2013 13:29:01 +0000 [thread overview]
Message-ID: <20130206132901.GL4720@opensource.wolfsonmicro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
The following changes since commit 88b62b915b0b7e25870eb0604ed9a92ba4bfc9f7:
Linux 3.8-rc6 (2013-02-01 12:08:14 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-v3.8-rc6
for you to fetch changes up to 53e5da79fa5222f2b810da7bf145e3a9f018dcc2:
Merge remote-tracking branch 'regulator/fix/tps65910' into tmp (2013-02-06 11:28:53 +0000)
----------------------------------------------------------------
regulator: Fixes for v3.8-rc7
Mostly driver specific fixes here, though one of them uncovered the
issue Stephen Warren fixed with multiple OF matches getting upset due to
a lack of cleanup.
----------------------------------------------------------------
Alim Akhtar (1):
regulator: s2mps11: fix incorrect register for buck10
Axel Lin (5):
regulator: tps65217: Fix using wrong dev argument for calling of_regulator_match
regulator: tps65910: Fix using wrong dev argument for calling of_regulator_match
regulator: max8907: Fix using wrong dev argument for calling of_regulator_match
regulator: max77686: Fix using wrong dev argument at various places
regulator: max8997: Fix using wrong dev argument at various places
Marek Szyprowski (1):
regulator: max8998: fix incorrect min_uV value for ldo10
Mark Brown (8):
Merge remote-tracking branch 'regulator/fix/max77686' into tmp
Merge remote-tracking branch 'regulator/fix/max8907' into tmp
Merge remote-tracking branch 'regulator/fix/max8997' into tmp
Merge remote-tracking branch 'regulator/fix/max8998' into tmp
Merge remote-tracking branch 'regulator/fix/of' into tmp
Merge remote-tracking branch 'regulator/fix/s2mps11' into tmp
Merge remote-tracking branch 'regulator/fix/tps65217' into tmp
Merge remote-tracking branch 'regulator/fix/tps65910' into tmp
Stephen Warren (1):
regulator: clear state each invocation of of_regulator_match
drivers/regulator/max77686.c | 15 ++++++------
drivers/regulator/max8907-regulator.c | 3 +--
drivers/regulator/max8997.c | 39 ++++++++++++++++----------------
drivers/regulator/max8998.c | 2 +-
drivers/regulator/of_regulator.c | 6 +++++
drivers/regulator/s2mps11.c | 4 ++--
drivers/regulator/tps65217-regulator.c | 4 ++--
drivers/regulator/tps65910-regulator.c | 2 +-
8 files changed, 40 insertions(+), 35 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-02-06 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 13:29 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-29 3:41 [GIT PULL] regulator updates for v3.8 Mark Brown
2013-01-15 2:17 Mark Brown
2012-12-13 2:30 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=20130206132901.GL4720@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Liam.R.Girdwood@intel.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;
as well as URLs for NNTP newsgroup(s).