From: Johan Hovold <johan@kernel.org>
To: Brian Masney <bmasney@redhat.com>
Cc: Shazad Hussain <quic_shazhuss@quicinc.com>,
andersson@kernel.org, sboyd@kernel.org, agross@kernel.org,
mturquette@baylibre.com, Konrad Dybcio <konrad.dybcio@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] clk: qcom: gcc-sc8280xp: add cxo as parent for three ufs ref clks
Date: Tue, 15 Nov 2022 14:01:04 +0100 [thread overview]
Message-ID: <Y3ONkOhcdK+gt46g@hovoldconsulting.com> (raw)
In-Reply-To: <Y3OLDj6xzOVjvEdV@x1>
On Tue, Nov 15, 2022 at 07:50:22AM -0500, Brian Masney wrote:
> On Tue, Nov 15, 2022 at 03:52:17PM +0530, Shazad Hussain wrote:
> > Added parent_data as CXO for three UFS reference clocks named,
> > gcc_ufs_ref_clkref_clk, gcc_ufs_card_clkref_clk and
> > gcc_ufs_1_card_clkref_clk.
> >
> > Fixes: d65d005f9a6c ("clk: qcom: add sc8280xp GCC driver")
> > Link: https://lore.kernel.org/lkml/Y2Tber39cHuOSR%2FW@hovoldconsulting.com/
> > Signed-off-by: Shazad Hussain <quic_shazhuss@quicinc.com>
>
> Put this Link beneath the --- since Bjorn will add one that's specific
> to your patch when he adds it to his tree.
I think it's ok to keep that Link if it was intended as a reference to
the discussions leading up to this patch. There can be more than one
Link tag, and this one is more in line with how Linus thinks they should
be used than the ones added by tooling such as b4 when applying.
Johan
next prev parent reply other threads:[~2022-11-15 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 10:22 [PATCH v2] clk: qcom: gcc-sc8280xp: add cxo as parent for three ufs ref clks Shazad Hussain
2022-11-15 12:08 ` Johan Hovold
2022-11-15 12:50 ` Andrew Halaney
2022-11-15 12:50 ` Brian Masney
2022-11-15 13:01 ` Johan Hovold [this message]
2022-11-15 13:03 ` Brian Masney
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=Y3ONkOhcdK+gt46g@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_shazhuss@quicinc.com \
--cc=sboyd@kernel.org \
--cc=vkoul@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