From: Tony Lindgren <tony@atomide.com>
To: green@linuxhacker.ru
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Regulator cleanups in mach-omap2, take three
Date: Tue, 14 Jun 2011 04:47:32 -0700 [thread overview]
Message-ID: <20110614114732.GR3352@atomide.com> (raw)
In-Reply-To: <1307386628-1153-1-git-send-email-green@linuxhacker.ru>
* green@linuxhacker.ru <green@linuxhacker.ru> [110606 11:54]:
> Hello!
>
> This is yet another attempt at some regulator cleanups in mach-omap2 code:
> Convert all users to REGULATOR_SUPPLY init style and drop the old-style
> .dev assignment common ins hs_mmc init.
>
> I made a test compile and all the individual board files changed compile
> (I don't have the devices themselves, but similar changes to my
> device board file are working).
>
> For the pandaboard changes - I am not sure what the proper names for those
> devices would be, so only converted the regulator to array.
>
> Big changes since v2:
> Per Felipe Balbi request converted all regulator supplies to arrays
> just in case.
> Also nuked an unneeded comment in cm-t35 board left after mmc.dev
> assignment removal.
Thanks, applying to devel-cleanup branch for next merge window.
Tony
prev parent reply other threads:[~2011-06-14 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 18:57 Regulator cleanups in mach-omap2, take three green
2011-06-06 18:57 ` [PATCH 1/2] cleanup regulator supply definitions in mach-omap2 green
2011-06-06 19:24 ` Felipe Balbi
2011-06-06 18:57 ` [PATCH 2/2] Remove old-style supply.dev assignments common in hsmmc init green
2011-06-06 19:25 ` Felipe Balbi
2011-06-14 11:47 ` Tony Lindgren [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=20110614114732.GR3352@atomide.com \
--to=tony@atomide.com \
--cc=green@linuxhacker.ru \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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).