From: Vinod Koul <vkoul@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>
Cc: heiko@sntech.de, robh+dt@kernel.org, kishon@ti.com,
linux-phy@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/4] dt-bindings: phy: rename phy nodename in phy-rockchip-inno-usb2.yaml
Date: Mon, 31 May 2021 14:05:08 +0530 [thread overview]
Message-ID: <YLSfvDeKrB0b66Ol@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20210518165658.12764-3-jbx6244@gmail.com>
On 18-05-21, 18:56, Johan Jonker wrote:
> The pattern: "^(|usb-|usb2-|usb3-|pci-|pcie-|sata-)phy(@[0-9a-f,]+)*$"
> in phy-provider.yaml has required "#phy-cells" for phy nodes.
> The "phy-cells" in rockchip-inno-usb2 nodes are located in subnodes.
> Rename the nodename to pattern "usb2phy@[0-9a-f]+$" to prevent
> notifications. Remove unneeded "#phy-cells" from parent node.
> Also sort example.
>
> make ARCH=arm dtbs_check
> DT_SCHEMA_FILES=~/.local/lib/python3.5/site-packages/dtschema/schemas/
> phy/phy-provider.yaml
This fails to apply for me, needs rebase..
--
~Vinod
next prev parent reply other threads:[~2021-05-31 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 16:56 [PATCH v6 0/4] convert grf.txt to YAML Johan Jonker
2021-05-18 16:56 ` [PATCH v6 1/4] dt-bindings: phy: convert rockchip-usb-phy.txt " Johan Jonker
2021-05-19 15:19 ` Rob Herring
2021-05-31 8:35 ` Vinod Koul
2021-05-18 16:56 ` [PATCH v6 2/4] dt-bindings: phy: rename phy nodename in phy-rockchip-inno-usb2.yaml Johan Jonker
2021-05-20 0:05 ` Rob Herring
2021-05-31 8:35 ` Vinod Koul [this message]
2021-05-18 16:56 ` [PATCH v6 3/4] ARM: dts: rockchip: rename nodename for phy-rockchip-inno-usb2 Johan Jonker
2021-05-18 16:56 ` [PATCH v6 4/4] arm64: " Johan Jonker
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=YLSfvDeKrB0b66Ol@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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).