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 v4.7
Date: Mon, 16 May 2016 12:19:51 +0100 [thread overview]
Message-ID: <20160516111951.GI2953@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
The following changes since commit 2a2cd5219023ea2e485c3e37486c24177a6da55a:
Merge remote-tracking branches 'regmap/fix/be', 'regmap/fix/doc' and 'regmap/fix/spmi' into regmap-linus (2016-05-13 10:36:10 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.7
for you to fetch changes up to d4ab78d7076d2a58a2d690b2f4a03a24d978ac1c:
Merge remote-tracking branches 'regmap/topic/doc' and 'regmap/topic/flat' into regmap-next (2016-05-13 10:36:14 +0100)
----------------------------------------------------------------
regmap: Updates for v4.7
The updates for this kernel release really are trivial:
- Check that max_register is set for the flat cache to avoid a crash
on initialization.
- Fix a typo in the documentation.
----------------------------------------------------------------
Alexander Stein (1):
regcache: flat: Require max_registers to be set
Andrew F. Davis (1):
regmap: cache: Fix typo in cache_bypass parameter description
Mark Brown (1):
Merge remote-tracking branches 'regmap/topic/doc' and 'regmap/topic/flat' into regmap-next
drivers/base/regmap/regcache-flat.c | 2 +-
drivers/base/regmap/regcache.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2016-05-16 11:20 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=20160516111951.GI2953@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
all inboxes | Powered by JetHome®