public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap fixes
Date: Fri, 6 Apr 2012 11:41:04 +0100	[thread overview]
Message-ID: <20120406104103.GH3172@opensource.wolfsonmicro.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

The following changes since commit dd775ae2549217d3ae09363e3edb305d0fa19928:

  Linux 3.4-rc1 (2012-03-31 16:24:09 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-3.4-fixes

for you to fetch changes up to c04c1b9ee8f30c7a3a25e20e406247003f634ebe:

  regmap: prevent division by zero in rbtree_show (2012-04-04 23:22:15 +0100)

----------------------------------------------------------------
regmap: A couple of small fixes for 3.4

Two more small fixes:
- Now we have users for it that aren't running Android it turns out that
  regcache_sync_region() is much more useful to drivers if it's exported
  for use by modules.  Who knew?
- Make sure we don't divide by zero when doing debugfs dumps of rbtrees,
  not visible up until now because everything was providing at least
  some cache on startup.

----------------------------------------------------------------
Mark Brown (1):
      regmap: Export regcache_sync_region()

Stephen Warren (1):
      regmap: prevent division by zero in rbtree_show

 drivers/base/regmap/regcache-rbtree.c |    8 +++++++-
 drivers/base/regmap/regcache.c        |    1 +
 2 files changed, 8 insertions(+), 1 deletions(-)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2012-04-06 10:41 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=20120406104103.GH3172@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.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