From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Liam Girdwood <lrg@ti.com>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] regulator updates for 3.4
Date: Tue, 8 May 2012 09:50:41 +0100 [thread overview]
Message-ID: <20120508085040.GD15893@opensource.wolfsonmicro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
The following changes since commit e816b57a337ea3b755de72bec38c10c864f23015:
Linux 3.4-rc3 (2012-04-15 18:28:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-3.4
for you to fetch changes up to 968c2c1707a3396ccd6e7e6c5ddaf658a6d3bd66:
regulator: Actually free the regulator in devm_regulator_put() (2012-05-07 13:14:44 +0100)
----------------------------------------------------------------
regulator: A couple of fixes for 3.4
One small fix for an edge condition in the max8997 driver and a fix for
a surprise in the devres API which caused devm_regulator_put() to not
actually put the regulator - a nicer version of this based on an
improvement of the devres API is queued for 3.5.
----------------------------------------------------------------
Axel Lin (1):
regulator: Fix the logic to ensure new voltage setting in valid range
Mark Brown (1):
regulator: Actually free the regulator in devm_regulator_put()
drivers/regulator/core.c | 5 ++++-
drivers/regulator/max8997.c | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-05-08 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 8:50 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-19 17:53 [GIT PULL] regulator updates for 3.4 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=20120508085040.GD15893@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--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