All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/4] cpufreq: OMAP: fixes for v3.7-rc2
Date: Mon, 08 Oct 2012 14:36:51 -0700	[thread overview]
Message-ID: <87k3v08x3g.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1505601.8trb51fSMV@vostro.rjw.lan> (Rafael J. Wysocki's message of "Sun, 07 Oct 2012 22:13:51 +0200")

"Rafael J. Wysocki" <rjw@sisk.pl> writes:

> On Wednesday 03 of October 2012 16:00:25 Kevin Hilman wrote:
>> From: Kevin Hilman <khilman@ti.com>
>> 
>> Here's a series with a couple bug fixes and a couple fixes that
>> make this driver support newer OMAP-based SoCs.
>> 
>> The 'get_cpu_device' patch is needed due to a change in the OMAP
>> OMAP PM core code which enforces use of get_cpu_device() instead of
>> a deprecated OMAP-specific API.
>> 
>> The usage of plat/*.h headers breaks single zImage, so platforms are
>> cleaning up and/or removing plat/*.h so the driver needs to be fixed
>> accordingly.
>> 
>> This series is based on the merge of Rafael's pm-for-3.7-rc1 tag into
>> Linus' master branch: commit 16642a2e7be23bbda013fc32d8f6c68982eab603.
>> 
>> Tested CPUfreq on OMAP platforms: 3430/n900, 3530/Overo,
>> 3730/OveroSTORM, 3730/Beagle-XM, 4430/Panda.
>> 
>> Rafael, if you're OK with this series, I'll get a pull request
>> ASAP so it can be included for v3.7-rc2.
>
> The patches are fine by me, but there may be a bit of a timing issue with
> them, because I'll be travelling between October 12 and October 21 inclusive
> and I won't be pushing stuff to kernel.org during that time.
>
> So I think it would be better to merge this material through the arm-soc tree,
> if that's not a problem.  If you decide to do so, please feel free to add my
> ACK to the patches.

Thanks, I'll get them queued.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] cpufreq: OMAP: fixes for v3.7-rc2
Date: Mon, 08 Oct 2012 14:36:51 -0700	[thread overview]
Message-ID: <87k3v08x3g.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1505601.8trb51fSMV@vostro.rjw.lan> (Rafael J. Wysocki's message of "Sun, 07 Oct 2012 22:13:51 +0200")

"Rafael J. Wysocki" <rjw@sisk.pl> writes:

> On Wednesday 03 of October 2012 16:00:25 Kevin Hilman wrote:
>> From: Kevin Hilman <khilman@ti.com>
>> 
>> Here's a series with a couple bug fixes and a couple fixes that
>> make this driver support newer OMAP-based SoCs.
>> 
>> The 'get_cpu_device' patch is needed due to a change in the OMAP
>> OMAP PM core code which enforces use of get_cpu_device() instead of
>> a deprecated OMAP-specific API.
>> 
>> The usage of plat/*.h headers breaks single zImage, so platforms are
>> cleaning up and/or removing plat/*.h so the driver needs to be fixed
>> accordingly.
>> 
>> This series is based on the merge of Rafael's pm-for-3.7-rc1 tag into
>> Linus' master branch: commit 16642a2e7be23bbda013fc32d8f6c68982eab603.
>> 
>> Tested CPUfreq on OMAP platforms: 3430/n900, 3530/Overo,
>> 3730/OveroSTORM, 3730/Beagle-XM, 4430/Panda.
>> 
>> Rafael, if you're OK with this series, I'll get a pull request
>> ASAP so it can be included for v3.7-rc2.
>
> The patches are fine by me, but there may be a bit of a timing issue with
> them, because I'll be travelling between October 12 and October 21 inclusive
> and I won't be pushing stuff to kernel.org during that time.
>
> So I think it would be better to merge this material through the arm-soc tree,
> if that's not a problem.  If you decide to do so, please feel free to add my
> ACK to the patches.

Thanks, I'll get them queued.

Kevin

  reply	other threads:[~2012-10-08 21:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 23:00 [PATCH 0/4] cpufreq: OMAP: fixes for v3.7-rc2 Kevin Hilman
2012-10-03 23:00 ` Kevin Hilman
2012-10-03 23:00 ` [PATCH 1/4] cpufreq: OMAP: ensure valid clock rate before scaling Kevin Hilman
2012-10-03 23:00   ` Kevin Hilman
2012-10-03 23:00 ` [PATCH 2/4] cpufreq: OMAP: remove unused <plat/omap-pm.h> Kevin Hilman
2012-10-03 23:00   ` Kevin Hilman
2012-10-03 23:00 ` [PATCH 3/4] cpufreq: OMAP: fix clock usage to be SoC independent, remove plat/ includes Kevin Hilman
2012-10-03 23:00   ` Kevin Hilman
2012-10-03 23:00 ` [PATCH 4/4] cpufreq: OMAP: use get_cpu_device() instead of omap_device API Kevin Hilman
2012-10-03 23:00   ` Kevin Hilman
2012-10-07 20:13 ` [PATCH 0/4] cpufreq: OMAP: fixes for v3.7-rc2 Rafael J. Wysocki
2012-10-07 20:13   ` Rafael J. Wysocki
2012-10-08 21:36   ` Kevin Hilman [this message]
2012-10-08 21:36     ` 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=87k3v08x3g.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.