All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Torvalds <linus@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap fixes for v3.8
Date: Tue, 15 Jan 2013 12:39:37 +0900	[thread overview]
Message-ID: <20130115033935.GE5701@opensource.wolfsonmicro.com> (raw)

The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:

  Linux 3.8-rc2 (2013-01-02 18:13:21 -0800)

are available in the git repository at:

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

for you to fetch changes up to e8d6539c8a94b88fc7ca5d6bdd9eeb0e64b434e4:

  regmap: debugfs: Make sure we store the last entry in the offset cache (2013-01-08 20:52:51 +0000)

----------------------------------------------------------------
regmap: Optimisation fixes for debugfs

The debugfs optimisations merged in v3.8 weren't my finest hour, there
were a number of cases that the more complex algorithm made worse
especially around the error handling. This patch series should address
those issues.

----------------------------------------------------------------
Mark Brown (5):
      regmap: debugfs: Fix attempts to read nonexistant register blocks
      regmap: debugfs: Fix check for block start in cached seeks
      regmap: debugfs: Discard the cache if we fail to allocate an entry
      regmap: debugfs: Ensure a correct return value for empty caches
      regmap: debugfs: Make sure we store the last entry in the offset cache

 drivers/base/regmap/regmap-debugfs.c |   53 +++++++++++++++++++++++++---------
 1 file changed, 40 insertions(+), 13 deletions(-)

                 reply	other threads:[~2013-01-15  3:39 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=20130115033935.GE5701@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linus@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.