From: Viresh Kumar <viresh.kumar@linaro.org>
To: Markus Mayer <mmayer@broadcom.com>, Rob Herring <robh+dt@kernel.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mark Rutland <mark.rutland@arm.com>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
Device Tree List <devicetree@vger.kernel.org>,
Power Management List <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] dt: cpufreq: brcm: New binding document for brcmstb-avs-cpufreq
Date: Fri, 14 Oct 2016 08:31:29 +0530 [thread overview]
Message-ID: <20161014030129.GF2991@vireshk-i7> (raw)
In-Reply-To: <1476310376-32699-2-git-send-email-mmayer@broadcom.com>
On 12-10-16, 15:12, Markus Mayer wrote:
> Add the binding document for the new brcmstb-avs-cpufreq driver.
>
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> .../bindings/cpufreq/brcm,stb-avs-cpu-freq.txt | 76 ++++++++++++++++++++++
> MAINTAINERS | 7 ++
> 2 files changed, 83 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/cpufreq/brcm,stb-avs-cpu-freq.txt
@Rob: Can you please review/Ack it ?
--
viresh
next prev parent reply other threads:[~2016-10-14 3:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 22:12 [PATCH v4 0/3] Broadcom STB AVS CPUfreq driver Markus Mayer
2016-10-12 22:12 ` [PATCH v4 1/3] dt: cpufreq: brcm: New binding document for brcmstb-avs-cpufreq Markus Mayer
2016-10-14 3:01 ` Viresh Kumar [this message]
2016-10-18 13:38 ` Rob Herring
2016-10-19 17:32 ` Markus Mayer
2016-10-12 22:12 ` [PATCH v4 2/3] cpufreq: brcmstb-avs-cpufreq: AVS CPUfreq driver for Broadcom STB SoCs Markus Mayer
2016-10-12 22:12 ` [PATCH v4 3/3] cpufreq: brcmstb-avs-cpufreq: add debugfs support Markus Mayer
2016-10-12 22:17 ` Markus Mayer
2016-10-14 16:05 ` Markus Mayer
2016-10-13 5:45 ` [PATCH v4 0/3] Broadcom STB AVS CPUfreq driver Viresh Kumar
2016-10-13 12:49 ` Rafael J. Wysocki
2016-10-14 3:02 ` 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=20161014030129.GF2991@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mmayer@broadcom.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome