From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Shinjo Park <peremen@gmail.com>
Cc: David Heidelberg <david@ixit.cz>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: phy: add definition for MSM8960
Date: Thu, 28 Jul 2022 16:10:01 +0200 [thread overview]
Message-ID: <84923720-30a6-1a49-48f6-96e078a46743@linaro.org> (raw)
In-Reply-To: <CAAs2AW7A4RfxAaKPsmJjA1s7s5_rnM2O4XAAFC=7x1Npttg5rQ@mail.gmail.com>
On 28/07/2022 15:54, Shinjo Park wrote:
> Hello Krzysztof,
>
> Sorry for any confusion during my first patch submission.
>
> PATCH 1:
>>> Change the reference of sleep_clk to the same as qcom-apq8064.dtsi.
>>
>> You add label, not change something.
>
>>> - sleep_clk {
>
>>> + sleep_clk: sleep_clk {
>
>>
>
>> Since you touch the line, make the device node sleep-clk (device node
>
>> names should not have underscores) and mention this in commit msg.
>
>
> I can change the line into "sleep_clk: sleep-clk". And the commit message
> would be "Change the device node of sleep_clk to sleep-clk and add a
> label"? Another problem is that in the same .dtsi file there are other
> device nodes containing underscores (cxo_board, pxo_board). Should I also
> change these in the patch?
>
> PATCH 2:
>>> + phy-names = "usb-phy";
>>> + status = "disabled";
>>
>> status is the last property.
>>
>>> + #reset-cells = <1>;
>
> I can move #reset-cells one line up and make the status last line. On the
> other hand, the same definition is also used in
> arch/arm/boot/dts/qcom-apq8064.dtsi (also the clock definition mentioned in
> PATCH 1). Shall I include another patch for that file in the next revision
> of this patch series?
Yes, you can rename them in other patch as well.
>
> PATH 3:
>> 1. Thread your submissions.
>
> Shall I use this thread for all follow-ups for my first and second patch?
No. One patchset, one thread.
https://elixir.bootlin.com/linux/v5.19-rc5/source/Documentation/process/5.Posting.rst
>
>> 2. Use subject prefix matching the file.
>
> If I understood correctly, then this should be "dt-bindings: phy:
> qcom,usb-hs-phy:"?
Yes.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-28 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 11:17 [PATCH 3/3] dt-bindings: phy: add definition for MSM8960 Shinjo Park
2022-07-28 11:47 ` Krzysztof Kozlowski
2022-07-28 11:54 ` David Heidelberg
2022-07-28 12:03 ` Krzysztof Kozlowski
[not found] ` <CAAs2AW7A4RfxAaKPsmJjA1s7s5_rnM2O4XAAFC=7x1Npttg5rQ@mail.gmail.com>
2022-07-28 14:10 ` Krzysztof Kozlowski [this message]
2022-07-30 8:15 ` [PATCH v2 3/3] dt-bindings: phy: qcom,usb-hs-phy: " Shinjo Park
2022-08-02 8:34 ` Krzysztof Kozlowski
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=84923720-30a6-1a49-48f6-96e078a46743@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=peremen@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).