From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cleanup regulator supply definitions in mach-omap2 to use REGULATOR_SUPPLY
Date: Mon, 23 May 2011 06:45:12 +0800 [thread overview]
Message-ID: <20110522224510.GA15858@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1306101529-22013-1-git-send-email-green@linuxhacker.ru>
On Sun, May 22, 2011 at 05:58:49PM -0400, green at linuxhacker.ru wrote:
> From: Oleg Drokin <green@linuxhacker.ru>
>
> Also drop old style supply.dev assignments common in hsmmc init
> as no longer needed.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Note that it'd be better to split into two patches as it makes review
easier.
next prev parent reply other threads:[~2011-05-22 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 21:58 [PATCH] cleanup regulator supply definitions in mach-omap2 to use REGULATOR_SUPPLY green at linuxhacker.ru
2011-05-22 22:45 ` Mark Brown [this message]
2011-05-22 22:49 ` Oleg Drokin
2011-05-22 22:56 ` 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=20110522224510.GA15858@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).