From: Rob Herring <robh@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
"David S . Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>, Roger Quadros <rogerq@ti.com>,
devicetree@vger.kernel.org,
Murali Karicheri <m-karicheri2@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-kernel@vger.kernel.org,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH net-next v2 4/9] dt-binding: ti: am65x: document mcu cpsw nuss
Date: Mon, 9 Mar 2020 15:37:11 -0500 [thread overview]
Message-ID: <20200309203711.GA15678@bogus> (raw)
In-Reply-To: <20200306234734.15014-5-grygorii.strashko@ti.com>
On Sat, 7 Mar 2020 01:47:29 +0200, Grygorii Strashko wrote:
> Document device tree bindings for The TI AM654x/J721E SoC Gigabit Ethernet MAC
> (Media Access Controller - CPSW2G NUSS). The CPSW NUSS provides Ethernet packet
> communication for the device.
>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> ---
> .../bindings/net/ti,k3-am654-cpsw-nuss.yaml | 225 ++++++++++++++++++
> 1 file changed, 225 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/ti,k3-am654-cpsw-nuss.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/net/ti,k3-am654-cpsw-nuss.example.dt.yaml: ethernet@46000000: 'pinctrl-0' is a dependency of 'pinctrl-names'
See https://patchwork.ozlabs.org/patch/1250679
Please check and re-submit.
next prev parent reply other threads:[~2020-03-09 20:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 23:47 [PATCH net-next v2 0/9] net: ethernet: ti: add networking support for k3 am65x/j721e soc Grygorii Strashko
2020-03-06 23:47 ` [PATCH net-next v2 1/9] net: ethernet: ti: ale: fix seeing unreg mcast packets with promisc and allmulti disabled Grygorii Strashko
2020-03-06 23:47 ` [PATCH net-next v2 2/9] net: ethernet: ti: ale: add support for mac-only mode Grygorii Strashko
2020-03-06 23:47 ` [PATCH net-next v2 3/9] net: ethernet: ti: ale: am65: add support for default thread cfg Grygorii Strashko
2020-03-06 23:47 ` [PATCH net-next v2 4/9] dt-binding: ti: am65x: document mcu cpsw nuss Grygorii Strashko
2020-03-09 20:37 ` Rob Herring [this message]
2020-03-06 23:47 ` [PATCH net-next v2 5/9] net: ethernet: ti: introduce am65x/j721e gigabit eth subsystem driver Grygorii Strashko
2020-03-07 1:20 ` Jakub Kicinski
2020-03-07 5:19 ` Grygorii Strashko
2020-03-09 19:36 ` Jakub Kicinski
2020-03-06 23:47 ` [PATCH net-next v2 6/9] arm64: dts: ti: k3-am65-mcu: add cpsw nuss node Grygorii Strashko
2020-03-06 23:47 ` [PATCH net-next v2 7/9] arm64: dts: k3-am654-base-board: add mcu cpsw nuss pinmux and phy defs Grygorii Strashko
2020-03-06 23:47 ` [PATCH net-next v2 8/9] arm64: dts: ti: k3-j721e-mcu: add mcu cpsw nuss node Grygorii Strashko
2020-03-06 23:47 ` [PATCH net-next v2 9/9] arm64: dts: ti: k3-j721e-common-proc-board: add mcu cpsw nuss pinmux and phy defs Grygorii Strashko
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=20200309203711.GA15678@bogus \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=rogerq@ti.com \
--cc=t-kristo@ti.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).