From: Xin Ji <xji@analogixsemi.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: bliang@analogixsemi.com, qwen@analogixsemi.com,
jli@analogixsemi.com, Rob Herring <robh@kernel.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v18 1/2] dt-bindings: usb: Add analogix anx7411 PD binding
Date: Thu, 14 Jul 2022 16:01:12 +0800 [thread overview]
Message-ID: <20220714080112.GA13028@anxtwsw-Precision-3640-Tower> (raw)
In-Reply-To: <f3c98e31-7c68-34a6-f492-95c1b6eeb625@linaro.org>
On Thu, Jul 14, 2022 at 08:52:09AM +0200, Krzysztof Kozlowski wrote:
> On 14/07/2022 04:02, Xin Ji wrote:
> > On Wed, Jul 13, 2022 at 11:28:16AM +0200, Krzysztof Kozlowski wrote:
> >> On 13/07/2022 10:41, Xin Ji wrote:
> >>> Add analogix PD chip anx7411 device binding
> >>>
> >>> Reviewed-by: Rob Herring <robh@kernel.org>
> >>> Signed-off-by: Xin Ji <xji@analogixsemi.com>
> >>>
> >>> ---
> >>> v17 -> v18 : Change node name from "usb_typec" to "typec"
> >>
> >> Node name was anx7411, not usb_typec. What are you changing here? The label?
> > Hi Krzysztof, sorry, I'm confused by your comment, this patch followed the
> > other dts example in other yaml file and passed the dts checking by
> > command "make dt_binding_check".
> >
> > Do you mean change the the node name "anx7411" to "typec"?
>
> Yes, since the some revisions ago I asked to use a generic name for the
> node (generic node name).
>
>
> Best regards,
> Krzysztof
Hi Krzysztof, OK, I'll change it in next version.
Thanks,
Xin
prev parent reply other threads:[~2022-07-14 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 8:41 [PATCH v18 1/2] dt-bindings: usb: Add analogix anx7411 PD binding Xin Ji
2022-07-13 9:28 ` Krzysztof Kozlowski
2022-07-14 2:02 ` Xin Ji
2022-07-14 6:52 ` Krzysztof Kozlowski
2022-07-14 8:01 ` Xin Ji [this message]
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=20220714080112.GA13028@anxtwsw-Precision-3640-Tower \
--to=xji@analogixsemi.com \
--cc=bliang@analogixsemi.com \
--cc=devicetree@vger.kernel.org \
--cc=jli@analogixsemi.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=qwen@analogixsemi.com \
--cc=robh@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).