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 fixes for v3.14
Date: Tue, 4 Mar 2014 17:08:54 +0800 [thread overview]
Message-ID: <20140304090854.GG13126@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
The following changes since commit acc3d5cec84f82ebea535fa0bd9500ac3df2aee9:
regulator: core: Change dummy supplies error message to a warning (2014-02-21 08:35:31 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-v3.14-rc5
for you to fetch changes up to 66fda75f47dc583f1c187556e9a2c082dd64f8c6:
regulator: core: Replace direct ops->disable usage (2014-02-25 10:31:45 +0900)
----------------------------------------------------------------
regulator: Fixes for v3.14-rc5
A couple of fixes here which ensure that regulators using the core
support for GPIO enables work in all cases by ensuring that helpers are
used consistently rather than open coding in places and hence not having
GPIO support in some of them.
----------------------------------------------------------------
Markus Pargmann (2):
regulator: core: Replace direct ops->enable usage
regulator: core: Replace direct ops->disable usage
drivers/regulator/core.c | 48 ++++++++++++++++++++----------------------------
1 file changed, 20 insertions(+), 28 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-03-04 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 9:08 Mark Brown [this message]
2014-03-04 16:43 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2014-03-04 7:37 Mark Brown
2014-03-04 7:27 Mark Brown
2014-02-23 4:24 Mark Brown
2014-02-12 16:51 Mark Brown
2014-02-05 15:16 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=20140304090854.GG13126@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®