mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>, Taniya Das <tdas@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Stephen Boyd <sboyd@kernel.org>,
	Rajendra Nayak <rnayak@codeaurora.org>,
	devicetree@vger.kernel.org, robh@kernel.org,
	skannan@codeaurora.org, linux-arm-msm@vger.kernel.org,
	evgreen@google.com, Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [PATCH v13 0/2] cpufreq: qcom-hw: Add support for QCOM cpufreq HW
Date: Mon, 17 Dec 2018 11:16:50 +0100	[thread overview]
Message-ID: <36800685.BEkRLjAyIo@aspire.rjw.lan> (raw)
In-Reply-To: <20181214044213.kae2yhogbrgomyu6@vireshk-i7>

On Friday, December 14, 2018 5:42:13 AM CET Viresh Kumar wrote:
> On 14-12-18, 09:40, Taniya Das wrote:
> >  [v13]
> >    * Update Documentation binding to #freq-domain-cells in description.
> >    * Replace devm_ioremap_resource() to use devm_ioremap() API.
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

The series has been applied, thanks!


      reply	other threads:[~2018-12-17 10:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  4:10 Taniya Das
2018-12-14  4:10 ` [PATCH v13 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ Firmware bindings Taniya Das
2018-12-14  5:32   ` Stephen Boyd
2018-12-17 20:45     ` Rob Herring
2018-12-17  7:56   ` Amit Kucheria
2018-12-17 20:50   ` Rob Herring
2018-12-14  4:10 ` [PATCH v13 2/2] cpufreq: qcom-hw: Add support for QCOM cpufreq HW driver Taniya Das
2018-12-14  5:36   ` Stephen Boyd
2018-12-14 17:30   ` Matthias Kaehlcke
2018-12-17  7:56   ` Amit Kucheria
2018-12-14  4:42 ` [PATCH v13 0/2] cpufreq: qcom-hw: Add support for QCOM cpufreq HW Viresh Kumar
2018-12-17 10:16   ` Rafael J. Wysocki [this message]

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=36800685.BEkRLjAyIo@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=devicetree@vger.kernel.org \
    --cc=evgreen@google.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=rnayak@codeaurora.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=skannan@codeaurora.org \
    --cc=tdas@codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®