All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Joseph Lo <josephl@nvidia.com>,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	Stephen Warren <swarren@nvidia.com>
Subject: [GIT PULL]: CPUFreq: ARM Fixes for 3.12
Date: Mon, 26 Aug 2013 11:48:00 +0530	[thread overview]
Message-ID: <CAKohpoksNiGT+r3JTY6KFwnDFA5OYE-vQe8W_9GT-fN21UMrfQ@mail.gmail.com> (raw)

Hi Rafael,

Hopefully this is the last patch for 3.12 for ARM CPUFreq subsystem.

The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:

  Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)

are available in the git repository at:

  git://git.linaro.org/people/vireshk/linux.git cpufreq-fixes

for you to fetch changes up to b192b910f3832793082c1a18262c4da0efe121ae:

  cpufreq: tegra: fix the wrong clock name (2013-08-23 21:58:28 +0530)

----------------------------------------------------------------
Joseph Lo (1):
      cpufreq: tegra: fix the wrong clock name

 drivers/cpufreq/tegra-cpufreq.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

             reply	other threads:[~2013-08-26  6:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  6:18 Viresh Kumar [this message]
2013-08-26 14:06 ` [GIT PULL]: CPUFreq: ARM Fixes for 3.12 Viresh Kumar
2013-08-27  0:52   ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2013-08-12  6:33 Viresh Kumar
2013-08-12  6:33 ` Viresh Kumar
2013-08-13 12:42 ` Rafael J. Wysocki
2013-08-13 12:42   ` Rafael J. Wysocki
2013-08-13 13:34   ` Viresh Kumar
2013-08-13 13:34     ` Viresh Kumar

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=CAKohpoksNiGT+r3JTY6KFwnDFA5OYE-vQe8W_9GT-fN21UMrfQ@mail.gmail.com \
    --to=viresh.kumar@linaro.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=josephl@nvidia.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=swarren@nvidia.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 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.