All of lore.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, Liam Girdwood <lrg@ti.com>
Subject: [GIT PULL] regulator fixes for 3.3
Date: Tue, 14 Feb 2012 14:11:33 -0800	[thread overview]
Message-ID: <20120214221132.GA4035@opensource.wolfsonmicro.com> (raw)

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

The following changes since commit d65b4e98d7ea3038b767b70fe8be959b2913f16d:

  Linux 3.3-rc3 (2012-02-08 19:21:53 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-linus

for you to fetch changes up to 9fc886a1880766fb91cb27c2e96bd814cef640d6:

  regulator: Fix getting voltage in max8649_enable_time() (2012-02-10 11:20:55 +0000)

----------------------------------------------------------------
One small bug fix from Axel plus a fix for a build failure in unrealstic
but commonly built configs which for some reason manage to survive for
an awfully long time in -next without any reports.
----------------------------------------------------------------

Axel Lin (1):
      regulator: Fix getting voltage in max8649_enable_time()

David Miller (1):
      regulator: Fix mc13xxx regulator modular build (again)

 drivers/regulator/max8649.c                |    2 +-
 drivers/regulator/mc13xxx-regulator-core.c |    2 ++
 2 files changed, 3 insertions(+), 1 deletions(-)

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

             reply	other threads:[~2012-02-14 22:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 22:11 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-14 13:07 [GIT PULL] regulator fixes for 3.3 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=20120214221132.GA4035@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --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 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.