From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] clk: qcom: Add some missing gcc clks for msm8996
Date: Mon, 13 Aug 2018 11:43:51 -0700 [thread overview]
Message-ID: <20180813184351.GG23866@tuxbook-pro> (raw)
In-Reply-To: <153391387168.37448.10798348572941173469@swboyd.mtv.corp.google.com>
On Fri 10 Aug 08:11 PDT 2018, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2018-08-09 15:01:19)
> > From: Rajendra Nayak <rnayak@codeaurora.org>
> >
> > Add a few missing gcc clks for msm8996
> >
> > Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> > [bjorn: omit aggre0_noc_qosgen_extref_clk]
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > ---
>
> This is still going on?! I'm going to ignore Rob's auto email on this
> patch.
>
There wasn't much "going on" since your last reply, found this on the
floor between some chairs...
The issue pointed to you on v1 was that there was another patch that
already added two of the clocks, so this v2 simply drops the two
duplicated clocks; i.e. solves the merge conflict.
What I see now is that I did forget to carry Rob's R-b from v1.
Regards,
Bjorn
next prev parent reply other threads:[~2018-08-13 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 22:01 [PATCH v2] clk: qcom: Add some missing gcc clks for msm8996 Bjorn Andersson
2018-08-10 15:11 ` Stephen Boyd
2018-08-13 18:43 ` Bjorn Andersson [this message]
2018-08-28 22:51 ` 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=20180813184351.GG23866@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@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).