All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH V2] regulator: add driver for MAX8660/8661
Date: Tue, 29 Sep 2009 17:46:44 +0100	[thread overview]
Message-ID: <1254242804.6623.312.camel@odin> (raw)
In-Reply-To: <1253864366-25459-1-git-send-email-w.sang@pengutronix.de>

On Fri, 2009-09-25 at 09:39 +0200, Wolfram Sang wrote:
> Tested with a MX25-based custom board.
> 
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
> ---
> 
> Have fun at LPC! :)
> 
> Changes since V1:
> 
> - dropped comment about forced PWM (superfluous)
> - use list-functions in set-functions
> 
> Changes since RFC:
> 
> - introduced EN34_IS_HIGH option in platform_data
> - documentation moved into the source
> - switched to use ?DTV2-registers instead of ?DTV1
>   (created easier to read bit-patterns, no functional change)
> - added a note that forced PWM does not save power here
> - improved comments & removed typos
> 
>  drivers/regulator/Kconfig         |    7 +
>  drivers/regulator/Makefile        |    1 +
>  drivers/regulator/max8660.c       |  510 +++++++++++++++++++++++++++++++++++++
>  include/linux/regulator/max8660.h |   57 ++++
>  4 files changed, 575 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/regulator/max8660.c
>  create mode 100644 include/linux/regulator/max8660.h

Back from LPC and applied to for-next.

Thanks

Liam


      parent reply	other threads:[~2009-09-29 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 13:24 [PATCH] regulator: add driver for MAX8660/8661 Wolfram Sang
2009-09-24 17:39 ` Mark Brown
2009-09-24 18:07   ` Wolfram Sang
2009-09-24 18:13     ` Mark Brown
2009-09-24 18:21     ` Liam Girdwood
2009-09-25  7:39       ` [PATCH V2] " Wolfram Sang
2009-09-25 17:23         ` Mark Brown
2009-09-29 16:46         ` Liam Girdwood [this message]

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=1254242804.6623.312.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w.sang@pengutronix.de \
    /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.