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: Lightweight patchset for regulator-framework
Date: Sat, 19 Sep 2009 11:33:28 +0100 [thread overview]
Message-ID: <1253356408.6008.1.camel@odin> (raw)
In-Reply-To: <1253306686-20616-1-git-send-email-w.sang@pengutronix.de>
On Fri, 2009-09-18 at 22:44 +0200, Wolfram Sang wrote:
> Hi,
>
> here is a small patch series fixing a few issues I found while working on a
> regulator driver. Might be nice to have in 2.6.32 already.
>
> Regards,
>
> Wolfram
>
Applied all.
Thanks
Liam
prev parent reply other threads:[~2009-09-19 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 20:44 Lightweight patchset for regulator-framework Wolfram Sang
2009-09-18 20:44 ` [PATCH 1/4] regulator: fix typos Wolfram Sang
2009-09-18 20:44 ` [PATCH 2/4] regulator: drop 'default n' Wolfram Sang
2009-09-18 20:44 ` [PATCH 3/4] regulator/lp3971: drop unnecessary initialization Wolfram Sang
2009-09-18 20:44 ` [PATCH 4/4] regulator/driver: be more specific in nanodoc for is_enabled Wolfram Sang
2009-09-18 21:14 ` Lightweight patchset for regulator-framework Mark Brown
2009-09-19 10:33 ` 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=1253356408.6008.1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox