From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap fixes for v3.13
Date: Fri, 13 Dec 2013 13:44:28 +0000 [thread overview]
Message-ID: <20131213134428.GC11044@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v3.13-rc3
for you to fetch changes up to 652787ab1aca35e5e85e644757f7ea2cc00681d1:
Merge remote-tracking branches 'regmap/fix/doc' and 'regmap/fix/mmio' into regmap-linus (2013-11-26 13:16:56 +0000)
----------------------------------------------------------------
regmap: Fixes for v3.13
Two small changes to fix some error handling and checking (both of which
would be quite serious if the errors trigger) plus a trivial
documentation fix.
----------------------------------------------------------------
Courtney Cavin (1):
regmap: make sure we unlock on failure in regmap_bulk_write
Gerhard Sittig (1):
regmap: trivial comment fix (copy'n'paste error)
Mark Brown (2):
Merge remote-tracking branch 'regmap/fix/core' into regmap-linus
Merge remote-tracking branches 'regmap/fix/doc' and 'regmap/fix/mmio' into regmap-linus
Stephen Warren (1):
regmap: use IS_ERR() to check clk_get() results
drivers/base/regmap/regmap-mmio.c | 11 ++++++-----
drivers/base/regmap/regmap.c | 8 ++++----
2 files changed, 10 insertions(+), 9 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-12-13 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131213134428.GC11044@sirena.org.uk \
--to=broonie@kernel.org \
--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