From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Steev Klimaszewski <steev@kali.org>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] clk: qcom: Add SC8280XP display clock controller
Date: Mon, 17 Oct 2022 21:02:30 -0400 [thread overview]
Message-ID: <c2aacd7c-1773-2ca7-415e-0b3ec7b5ef02@linaro.org> (raw)
In-Reply-To: <bc96324f-c560-3baf-a771-beef6955a537@kali.org>
On 17/10/2022 20:51, Steev Klimaszewski wrote:
> Round 2 because the patch is too long for the mailing lists, I hope it
> is okay to strip out a bit of the patch
Yes, it is okay, actually expected and much better way. There is no need
to scroll a lot of message looking for a tag.
Thank you!
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-18 1:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 20:37 [PATCH v2 0/2] clock: qcom: SC8280XP display clock controller Bjorn Andersson
2022-09-26 20:37 ` [PATCH v2 1/2] dt-bindings: clock: Add Qualcomm SC8280XP display clock bindings Bjorn Andersson
2022-09-26 20:38 ` [PATCH v2 2/2] clk: qcom: Add SC8280XP display clock controller Bjorn Andersson
2022-10-17 23:09 ` Steev Klimaszewski
2022-10-18 0:51 ` Steev Klimaszewski
2022-10-18 1:02 ` Krzysztof Kozlowski [this message]
2022-11-08 16:56 ` Konrad Dybcio
2022-11-10 4:09 ` (subset) [PATCH v2 0/2] clock: qcom: " Bjorn Andersson
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=c2aacd7c-1773-2ca7-415e-0b3ec7b5ef02@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@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_bjorande@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=steev@kali.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).