From: davej@redhat.com (Dave Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] cpufreq: OMAP: move to drivers/cpufreq and updates for v3.3
Date: Fri, 2 Dec 2011 12:52:57 -0500 [thread overview]
Message-ID: <20111202175256.GA27874@redhat.com> (raw)
In-Reply-To: <87ty5ij2aa.fsf@ti.com>
On Fri, Dec 02, 2011 at 09:45:17AM -0800, Kevin Hilman wrote:
> Dave,
>
> Kevin Hilman <khilman@ti.com> writes:
>
> > Hi Dave,
> >
> > Here's the updated pull request after a rebase onto v3.2-rc1 and some
> > fixes to address other changes that went into v3.2.
> >
> > This is targetted for v3.3, so I'd like to get it into your tree and
> > into linux-next.
>
> Are there any problems with this series or pull request?
Somehow I missed this. I'll get to it this afternoon and push it out.
apologies.
Dave.
next prev parent reply other threads:[~2011-12-02 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 21:20 [GIT PULL] cpufreq: OMAP: move to drivers/cpufreq and updates for v3.3 Kevin Hilman
2011-12-02 17:45 ` Kevin Hilman
2011-12-02 17:52 ` Dave Jones [this message]
2011-12-02 19:45 ` Dave Jones
2011-12-02 21:19 ` Kevin Hilman
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=20111202175256.GA27874@redhat.com \
--to=davej@redhat.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).