From: Kevin Hilman <khilman@ti.com>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@vger.kernel.org, linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] cpufreq: OMAP updates for v3.4
Date: Thu, 15 Mar 2012 10:00:35 -0700 [thread overview]
Message-ID: <4F622033.6030403@ti.com> (raw)
In-Reply-To: <20120307203031.GA7672@redhat.com>
Hi Dave,
On 03/07/2012 12:30 PM, Dave Jones wrote:
> On Wed, Mar 07, 2012 at 12:20:41PM -0800, Kevin Hilman wrote:
> > Dave,
> >
> > Please pull the following OMAP CPUfreq driver changes for v3.4.
>
> pulled, thanks.
Looks like these got pulled into your fixes branch, but I don't see them
in linux-next? Are these on their way upstream?
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] cpufreq: OMAP updates for v3.4
Date: Thu, 15 Mar 2012 10:00:35 -0700 [thread overview]
Message-ID: <4F622033.6030403@ti.com> (raw)
In-Reply-To: <20120307203031.GA7672@redhat.com>
Hi Dave,
On 03/07/2012 12:30 PM, Dave Jones wrote:
> On Wed, Mar 07, 2012 at 12:20:41PM -0800, Kevin Hilman wrote:
> > Dave,
> >
> > Please pull the following OMAP CPUfreq driver changes for v3.4.
>
> pulled, thanks.
Looks like these got pulled into your fixes branch, but I don't see them
in linux-next? Are these on their way upstream?
Kevin
next prev parent reply other threads:[~2012-03-15 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 20:20 [GIT PULL] cpufreq: OMAP updates for v3.4 Kevin Hilman
2012-03-07 20:20 ` Kevin Hilman
2012-03-07 20:30 ` Dave Jones
2012-03-07 20:30 ` Dave Jones
2012-03-15 17:00 ` Kevin Hilman [this message]
2012-03-15 17:00 ` Kevin Hilman
2012-03-14 16:41 ` Grazvydas Ignotas
2012-03-14 16:41 ` Grazvydas Ignotas
2012-03-14 16:44 ` Dave Jones
2012-03-14 16:44 ` Dave Jones
2012-03-14 17:22 ` Kevin Hilman
2012-03-14 17:22 ` Kevin Hilman
2012-03-14 17:38 ` Grazvydas Ignotas
2012-03-14 17:38 ` Grazvydas Ignotas
2012-03-15 14:25 ` Kevin Hilman
2012-03-15 14:25 ` 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=4F622033.6030403@ti.com \
--to=khilman@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.