From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap updates for v3.14
Date: Mon, 20 Jan 2014 15:51:57 +0000 [thread overview]
Message-ID: <20140120155157.GP17314@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
The following changes since commit d6e0a2dd12f4067a5bcefb8bbd8ddbeff800afbc:
Linux 3.13-rc7 (2014-01-04 15:12:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v3.14
for you to fetch changes up to 86776fc174973e556be7d668763f509a81124f8b:
Merge remote-tracking branch 'regmap/topic/ack' into regmap-next (2014-01-09 14:34:13 +0000)
----------------------------------------------------------------
regmap: Updates for v3.14
Nothing terribly exciting with regmap this release, mainly a few small
extensions to allow more devices to be supported:
- Allow the bulk I/O APIs to be used with no-bus regmaps.
- Support interrupt controllers with zero ack base.
- Warning and spelling fixes.
----------------------------------------------------------------
Alexander Shiyan (1):
regmap: irq: Allow using zero value for ack_base
Cai Zhiyong (1):
regmap: Fix 'ret' would return an uninitialized value
Laszlo Papp (1):
regmap: fix a couple of typos
Mark Brown (3):
Merge tag 'v3.13-rc4' into regmap-core
Merge remote-tracking branch 'regmap/topic/core' into regmap-next
Merge remote-tracking branch 'regmap/topic/ack' into regmap-next
Stephen Boyd (2):
regmap: Allow regmap_bulk_read() to work for "no-bus" regmaps
regmap: Allow regmap_bulk_write() to work for "no-bus" regmaps
drivers/base/regmap/regmap-irq.c | 6 ++--
drivers/base/regmap/regmap.c | 72 +++++++++++++++++++++++-----------------
include/linux/regmap.h | 15 +++++----
3 files changed, 54 insertions(+), 39 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2014-01-20 15:52 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=20140120155157.GP17314@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
Powered by JetHome