public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Paul Mundt <lethal@linux-sh.org>,
	Tony Lindgren <tony@atomide.com>,
	Mike Frysinger <vapier@gentoo.org>,
	linux-sh@vger.kernel.org, linux-omap@vger.kernel.org,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH] regulator: provide dummy supply support
Date: Fri, 28 Oct 2011 23:57:03 +0200	[thread overview]
Message-ID: <20111028215703.GB30339@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1319833618-25190-1-git-send-email-s.hauer@pengutronix.de>

On Fri, Oct 28, 2011 at 10:26:57PM +0200, Sascha Hauer wrote:

> The following patch allows it for boards to register a dummy supply for
> devices for which no software controllable regulator is available. The
> current CONFIG_REGULATOR_DUMMY and (unused) regulator_use_dummy_regulator()

Please don't send cover letters for single patch serieses, if there's
content it should probably be in the changelog...

  parent reply	other threads:[~2011-10-28 21:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28 20:26 [PATCH] regulator: provide dummy supply support Sascha Hauer
2011-10-28 20:26 ` [PATCH] regulator: Provide " Sascha Hauer
2011-10-28 21:59   ` Mark Brown
2011-10-28 22:47     ` Sascha Hauer
2011-10-28 23:16       ` Mike Frysinger
2011-10-29 17:42       ` Mark Brown
2011-11-01 17:50       ` Mike Frysinger
2011-11-01 18:27         ` Mark Brown
2011-11-02 10:03           ` Sascha Hauer
2011-11-02 10:41             ` Mark Brown
2011-11-02 14:29               ` Sascha Hauer
2011-10-28 21:57 ` Mark Brown [this message]
2011-10-28 23:22   ` [PATCH] regulator: provide " Mike Frysinger

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=20111028215703.GB30339@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=lethal@linux-sh.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=s.hauer@pengutronix.de \
    --cc=tony@atomide.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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