From: <ansuelsmth@gmail.com>
To: "'Rob Herring'" <robh@kernel.org>
Cc: <sboyd@kernel.org>, "'John Crispin'" <john@phrozen.org>,
"'Andy Gross'" <agross@kernel.org>,
"'Bjorn Andersson'" <bjorn.andersson@linaro.org>,
"'Michael Turquette'" <mturquette@baylibre.com>,
"'Mark Rutland'" <mark.rutland@arm.com>,
<linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: R: [PATCH v2] clk: qcom: clk-rpm: add missing rpm clk for ipq806x
Date: Wed, 11 Mar 2020 13:46:02 +0100 [thread overview]
Message-ID: <06a501d5f7a3$06ba72f0$142f58d0$@gmail.com> (raw)
In-Reply-To: <20200310184109.GA2508@bogus>
> On Tue, 10 Mar 2020 15:37:56 +0100, Ansuel Smith wrote:
> > Add missing definition of rpm clk for ipq806x soc
> >
> > Signed-off-by: John Crispin <john@phrozen.org>
> > Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
> > Acked-by: John Crispin <john@phrozen.org>
> > ---
> > .../devicetree/bindings/clock/qcom,rpmcc.txt | 1 +
> > drivers/clk/qcom/clk-rpm.c | 35 +++++++++++++++++++
> > include/dt-bindings/clock/qcom,rpmcc.h | 4 +++
> > 3 files changed, 40 insertions(+)
> >
>
> Please add Acked-by/Reviewed-by tags when posting new versions.
> However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
>
> If a tag was not added on purpose, please state why and what changed.
Sorry it was asked to resend this as there was a bug in the software used to
apply this.
next prev parent reply other threads:[~2020-03-11 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 14:37 [PATCH v2] clk: qcom: clk-rpm: add missing rpm clk for ipq806x Ansuel Smith
2020-03-10 18:41 ` Rob Herring
2020-03-11 12:46 ` ansuelsmth [this message]
2020-03-13 20:57 ` Stephen Boyd
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='06a501d5f7a3$06ba72f0$142f58d0$@gmail.com' \
--to=ansuelsmth@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).