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 updates for 3.5
Date: Mon, 11 Jun 2012 11:21:16 +0800	[thread overview]
Message-ID: <20120611032115.GB4218@opensource.wolfsonmicro.com> (raw)

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

The following changes since commit f8f5701bdaf9134b1f90e5044a82c66324d2073f:

  Linux 3.5-rc1 (2012-06-02 18:29:26 -0700)

are available in the git repository at:

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

for you to fetch changes up to 752a6a5f84bfed18d0709383913d9d9d21b61c77:

  regmap: Export regmap_reinit_cache() (2012-06-08 05:57:21 +0800)

----------------------------------------------------------------
regmap: Fixes for 3.5

Nothing too exciting - a cleanup for debugfs in error handling and a fix
for the padding (which has only just acquired real use) and exporting a
function that's supposed to be usable by drivers.

----------------------------------------------------------------
Fabio Estevam (1):
      regmap: Fix the size calculation for map->format.buf_size

Mark Brown (1):
      regmap: Export regmap_reinit_cache()

Stephen Warren (1):
      regmap: clean up debugfs if regmap_init fails

 drivers/base/regmap/regmap.c |   10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

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

             reply	other threads:[~2012-06-11  3:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  3:21 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-05-21 10:38 [GIT PULL] regmap updates for 3.5 Mark Brown

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=20120611032115.GB4218@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