From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] Remove old-style supply.dev assignments common in hsmmc init
Date: Mon, 6 Jun 2011 22:25:05 +0300 [thread overview]
Message-ID: <20110606192503.GP12242@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1307386628-1153-3-git-send-email-green@linuxhacker.ru>
On Mon, Jun 06, 2011 at 02:57:08PM -0400, green at linuxhacker.ru wrote:
> From: Oleg Drokin <green@linuxhacker.ru>
>
> CC: Mark Brown <broonie@opensource.wolfsonmicro.com>
> CC: Mike Rapoport <mike@compulab.co.il>
> CC: Nishant Kamat <nskamat@ti.com>
> CC: Steve Sakoman <steve@sakoman.com>
> CC: Felipe Balbi <balbi@ti.com>
> Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
Acked-by: Felipe Balbi <balbi@ti.com>
compile tested with omap2plus_defconfig.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110606/da22da57/attachment.sig>
next prev parent reply other threads:[~2011-06-06 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1307386628-1153-1-git-send-email-green@linuxhacker.ru>
[not found] ` <1307386628-1153-2-git-send-email-green@linuxhacker.ru>
2011-06-06 19:24 ` [PATCH 1/2] cleanup regulator supply definitions in mach-omap2 Felipe Balbi
[not found] ` <1307386628-1153-3-git-send-email-green@linuxhacker.ru>
2011-06-06 19:25 ` Felipe Balbi [this message]
2011-06-14 11:47 ` Regulator cleanups in mach-omap2, take three Tony Lindgren
[not found] <1307342762-25363-1-git-send-email-green@linuxhacker.ru>
[not found] ` <1307342762-25363-3-git-send-email-green@linuxhacker.ru>
2011-06-06 9:22 ` [PATCH 2/2] Remove old-style supply.dev assignments common in hsmmc init Felipe Balbi
2011-06-06 10:13 ` Grazvydas Ignotas
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=20110606192503.GP12242@legolas.emea.dhcp.ti.com \
--to=balbi@ti.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).