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.18
Date: Fri, 7 Nov 2014 11:06:15 +0000 [thread overview]
Message-ID: <20141107110615.GI8509@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
The following changes since commit 0df1f2487d2f0d04703f142813d53615d62a1da4:
Linux 3.18-rc3 (2014-11-02 15:01:51 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-v3.18-rc3
for you to fetch changes up to 2a7509b187cab859cbc80e399e1d7c79c589d7ca:
Merge remote-tracking branches 'regulator/fix/max1586', 'regulator/fix/max77686', 'regulator/fix/max77693', 'regulator/fix/max77802', 'regulator/fix/max8860' and 'regulator/fix/s2mpa01' into regulator-linus (2014-11-05 14:59:25 +0000)
----------------------------------------------------------------
regulator: Fixes for v3.18
More changes than I'd like here, most of them for a single bug repeated
in a bunch of drivers with data not being initialized correctly, plus a
fix to lower the severity of a warning introduced in the last merge
window which can legitimately go off so we don't want to alarm users
excessively.
----------------------------------------------------------------
Javier Martinez Canillas (5):
regulator: max1586: zero-initialize regulator match table array
regulator: max77686: zero-initialize regulator match table
regulator: max77802: zero-initialize regulator match table
regulator: max8660: zero-initialize regulator match table array
regulator: s2mpa01: zero-initialize regulator match table array
Krzysztof Kozlowski (1):
regulator: max77693: Fix use of uninitialized regulator config
Mark Brown (3):
regulator: of: Lower the severity of the error with no container
Merge remote-tracking branch 'regulator/fix/core' into regulator-linus
Merge remote-tracking branches 'regulator/fix/max1586', 'regulator/fix/max77686', 'regulator/fix/max77693', 'regulator/fix/max77802', 'regulator/fix/max8860' and 'regulator/fix/s2mpa01' into regulator-linus
drivers/regulator/max1586.c | 2 +-
drivers/regulator/max77686.c | 2 +-
drivers/regulator/max77693.c | 2 +-
drivers/regulator/max77802.c | 2 +-
drivers/regulator/max8660.c | 2 +-
drivers/regulator/of_regulator.c | 3 ++-
drivers/regulator/s2mpa01.c | 2 +-
7 files changed, 8 insertions(+), 7 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2014-11-07 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 11:06 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-27 11:37 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=20141107110615.GI8509@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®