From: Rob Herring <robh@kernel.org>
To: Yifeng Zhao <yifeng.zhao@rock-chips.com>
Cc: devicetree@vger.kernel.org, kishon@ti.com, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org, vkoul@kernel.org,
cl@rock-chips.com, linux-phy@lists.infradead.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
p.zabel@pengutronix.de, linux-kernel@vger.kernel.org,
michael.riesch@wolfvision.net
Subject: Re: [PATCH v3 1/3] dt-bindings: phy: rockchip: Add Naneng combo PHY bindings
Date: Wed, 27 Oct 2021 17:03:51 -0500 [thread overview]
Message-ID: <YXnMxyuH/aGAvYAY@robh.at.kernel.org> (raw)
In-Reply-To: <20211025080632.32063-2-yifeng.zhao@rock-chips.com>
On Mon, 25 Oct 2021 16:06:30 +0800, Yifeng Zhao wrote:
> Add the compatible strings for the Naneng combo PHY found on rockchip SoC.
>
> Signed-off-by: Yifeng Zhao <yifeng.zhao@rock-chips.com>
> ---
>
> Changes in v3: None
> Changes in v2:
> - Fix dtschema/dtc warnings/errors
>
> .../phy/phy-rockchip-naneng-combphy.yaml | 98 +++++++++++++++++++
> 1 file changed, 98 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/phy-rockchip-naneng-combphy.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2021-10-27 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 8:06 [PATCH v3 0/3] Add Naneng combo PHY support for RK3568 Yifeng Zhao
2021-10-25 8:06 ` [PATCH v3 1/3] dt-bindings: phy: rockchip: Add Naneng combo PHY bindings Yifeng Zhao
2021-10-27 22:03 ` Rob Herring [this message]
2021-11-14 11:32 ` Johan Jonker
2021-10-25 8:06 ` [PATCH v3 2/3] phy/rockchip: add naneng combo phy for RK3568 Yifeng Zhao
2021-11-08 2:50 ` Kever Yang
2021-11-08 9:35 ` Philipp Zabel
2021-11-14 11:40 ` Johan Jonker
2021-12-07 13:51 ` Johan Jonker
2021-12-10 9:52 ` 赵仪峰
2021-10-25 8:06 ` [PATCH v3 3/3] arm64: dts: rockchip: add naneng combo phy nodes for rk3568 Yifeng Zhao
2021-11-14 11:33 ` 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=YXnMxyuH/aGAvYAY@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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=michael.riesch@wolfvision.net \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=yifeng.zhao@rock-chips.com \
/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).