All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Shawn Guo <shawn.guo@linaro.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	Sachin Kamat <spk.linux@gmail.com>,
	Thomas Abraham <thomas.ab@samsung.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	"pramod.gurav@smartplayin.com" <pramod.gurav@smartplayin.com>,
	Rob Herring <rob.herring@linaro.org>,
	Mike Turquette <mike.turquette@linaro.org>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	Tawfik Bayouk <tawfik@marvell.com>,
	Nadav Haklai <nadavh@marvell.com>,
	Lior Amsalem <alior@marvell.com>
Subject: Re: [PATCH v3 0/3] cpufreq: cpufreq-dt: platform_data based proposal
Date: Tue, 21 Oct 2014 15:33:09 +0200	[thread overview]
Message-ID: <2513404.oZkEVY1Jti@vostro.rjw.lan> (raw)
In-Reply-To: <1413711029-17419-1-git-send-email-thomas.petazzoni@free-electrons.com>

On Sunday, October 19, 2014 11:30:26 AM Thomas Petazzoni wrote:
> Hello Rafael,
> 
> As you requested, here is a new version of the cpufreq-dt patches,
> rebased on top of the latest Linus tree
> (52d589a01d4545ce1dc5c3892bb8c7b55edfe714 as I write this).
> 
> Compared to version 2:
> 
>  - Rebased on top of latest Linus tree.
> 
>  - Removed PATCH 3/4, which is meant to go through the mvebu
>    maintainer tree. I'll push it post-rc1.
> 
>  - Added Acked-by tags from Viresh, since he ACKed all the patches.
> 
> Could you take those patches and push them to 3.18 ?

I've applied the series and it is in my linux-next branch now (which means that
it should appear in linux-next proper tomorrow).

I'm going to push it for 3.18-rc2.

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  parent reply	other threads:[~2014-10-21 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-19  9:30 [PATCH v3 0/3] cpufreq: cpufreq-dt: platform_data based proposal Thomas Petazzoni
2014-10-19  9:30 ` [PATCH v3 1/3] cpufreq: allow driver-specific data Thomas Petazzoni
2014-10-19  9:30 ` [PATCH v3 2/3] cpufreq: cpufreq-dt: extend with platform_data Thomas Petazzoni
2014-10-19  9:30 ` [PATCH v3 3/3] cpufreq: cpufreq-dt: adjust message related to regulators Thomas Petazzoni
2014-10-21 13:33 ` Rafael J. Wysocki [this message]
2014-10-21 13:13   ` [PATCH v3 0/3] cpufreq: cpufreq-dt: platform_data based proposal Thomas Petazzoni
2014-10-27 13:54   ` Geert Uytterhoeven

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=2513404.oZkEVY1Jti@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=alior@marvell.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mike.turquette@linaro.org \
    --cc=nadavh@marvell.com \
    --cc=pramod.gurav@smartplayin.com \
    --cc=rob.herring@linaro.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=sboyd@codeaurora.org \
    --cc=shawn.guo@linaro.org \
    --cc=spk.linux@gmail.com \
    --cc=tawfik@marvell.com \
    --cc=thomas.ab@samsung.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=viresh.kumar@linaro.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.