From: Tony Lindgren <tony@atomide.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Kevin Hilman <khilman@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: OMAP2+: PM: core support for SMPS regulators for v3.4
Date: Tue, 27 Mar 2012 10:04:45 -0700 [thread overview]
Message-ID: <20120327170445.GP9859@atomide.com> (raw)
In-Reply-To: <CANOLnOMfsdGn-B0zftcV-zh+tSCGgmf0g1BsrFB0+Kh-HnNq0g@mail.gmail.com>
* Grazvydas Ignotas <notasas@gmail.com> [120327 07:00]:
> On Tue, Mar 13, 2012 at 1:28 AM, Kevin Hilman <khilman@ti.com> wrote:
> > Tony, updated pull request below. This includes all the TWL depencies
> > merged from the 'topic/twl' tag in Mark's tree.
> >
>
> Has this been lost now? It seems regulator parts got merged, but
> voltage parts are missing from Arnd's pull requests and are not
> showing up in linux-next.
> Was looking forward for voltage control in 3.4 to achieve higher clock
> rates on our aging OMAP3 hardware.
Sounds like this is something we should get merged early to arm-soc
tree after the merge window.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-27 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 20:14 [GIT PULL] ARM: OMAP2+: PM: core support for SMPS regulators for v3.4 Kevin Hilman
2012-03-08 2:18 ` Tony Lindgren
2012-03-08 18:09 ` Kevin Hilman
2012-03-09 0:32 ` Tony Lindgren
2012-03-09 11:47 ` Mark Brown
2012-03-09 15:29 ` Kevin Hilman
2012-03-11 20:42 ` Mark Brown
2012-03-12 17:26 ` Kevin Hilman
2012-03-12 17:32 ` Mark Brown
2012-03-12 23:28 ` Kevin Hilman
2012-03-27 13:57 ` Grazvydas Ignotas
2012-03-27 17:04 ` Tony Lindgren [this message]
2012-03-27 17:49 ` Kevin Hilman
2012-04-03 18:44 ` Tony Lindgren
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=20120327170445.GP9859@atomide.com \
--to=tony@atomide.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
/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).