From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, lgirdwood@gmail.com
Subject: [GIT PULL] regulator fix for v4.7
Date: Tue, 17 May 2016 19:18:16 +0100 [thread overview]
Message-ID: <20160517181816.GI8104@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
The following changes since commit 4f38c566a0967ce9291537ba04891391681a7661:
Merge remote-tracking branches 'regulator/topic/tps6524x' and 'regulator/topic/twl' into regulator-next (2016-05-13 14:23:49 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-can-change-voltage
for you to fetch changes up to ec4c436652cfdf5dcad60f553020ee99596b937b:
regulator: Silence build warnings from regulator_can_change_voltage() (2016-05-17 18:06:18 +0100)
----------------------------------------------------------------
regulator: Fix build warnings from regulator_can_change_voltage()
Cut down on noise for mainstream users of the API and people doing build
testing by dropping the deprecated flag from regulator_can_change_voltage()
as it triggers even on the EXPORT_SYMBOL_GPL() which affects all builds
rather than just the remaining drivers with calls to it (for which fixes
are currently pending).
The function remains deprecated and is expected to be removed entirely
in v4.8.
----------------------------------------------------------------
Mark Brown (1):
regulator: Silence build warnings from regulator_can_change_voltage()
include/linux/regulator/consumer.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2016-05-17 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 18:18 Mark Brown [this message]
2016-07-12 14:51 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=20160517181816.GI8104@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®