From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: OMAP: PM fixes for v3.6-rc
Date: Fri, 10 Aug 2012 23:24:27 -0700 [thread overview]
Message-ID: <20120811062427.GU11011@atomide.com> (raw)
In-Reply-To: <878vdmfxpx.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120810 10:45]:
> Tony,
>
> Please pull the following PM related fixes for v3.6-rc.
>
> One of them is a fix for drivers/cpufreq/omap-cpufreq.c, but it needs to
> go along with the arch/arm change. I'm listed in MAINTAINERS for the
> OMAP CPUfreq driver now, so this should be OK.
OK thanks pulling into fixes.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: PM fixes for v3.6-rc
Date: Fri, 10 Aug 2012 23:24:27 -0700 [thread overview]
Message-ID: <20120811062427.GU11011@atomide.com> (raw)
In-Reply-To: <878vdmfxpx.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120810 10:45]:
> Tony,
>
> Please pull the following PM related fixes for v3.6-rc.
>
> One of them is a fix for drivers/cpufreq/omap-cpufreq.c, but it needs to
> go along with the arch/arm change. I'm listed in MAINTAINERS for the
> OMAP CPUfreq driver now, so this should be OK.
OK thanks pulling into fixes.
Tony
next prev parent reply other threads:[~2012-08-11 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 17:44 [GIT PULL] ARM: OMAP: PM fixes for v3.6-rc Kevin Hilman
2012-08-10 17:44 ` Kevin Hilman
2012-08-11 6:24 ` Tony Lindgren [this message]
2012-08-11 6:24 ` 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=20120811062427.GU11011@atomide.com \
--to=tony@atomide.com \
--cc=khilman@ti.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.