From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
Scott Branden <sbranden@broadcom.com>,
linux-arm-kernel@lists.infradead.org, Ray Jui <rjui@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH v2] dt-bindings: net: Convert MDIO mux bindings to DT schema
Date: Tue, 1 Jun 2021 18:48:55 -0500 [thread overview]
Message-ID: <20210601234855.GA1357013@robh.at.kernel.org> (raw)
In-Reply-To: <20210526181411.2888516-1-robh@kernel.org>
On Wed, 26 May 2021 13:14:11 -0500, Rob Herring wrote:
> Convert the common MDIO mux bindings to DT schema.
>
> Drop the example from mdio-mux.yaml as mdio-mux-gpio.yaml has the same one.
>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Ray Jui <rjui@broadcom.com>
> Cc: Scott Branden <sbranden@broadcom.com>
> Cc: bcm-kernel-feedback-list@broadcom.com
> Cc: Andrew Lunn <andrew@lunn.ch>
> Cc: Heiner Kallweit <hkallweit1@gmail.com>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: netdev@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> v2:
> - Fix copy-n-paste error: s/I2C/MDIO/
> ---
> .../bindings/net/brcm,mdio-mux-iproc.txt | 2 +-
> .../devicetree/bindings/net/mdio-mux-gpio.txt | 119 ---------------
> .../bindings/net/mdio-mux-gpio.yaml | 135 ++++++++++++++++++
> .../bindings/net/mdio-mux-mmioreg.txt | 75 ----------
> .../bindings/net/mdio-mux-mmioreg.yaml | 78 ++++++++++
> .../bindings/net/mdio-mux-multiplexer.txt | 82 -----------
> .../bindings/net/mdio-mux-multiplexer.yaml | 82 +++++++++++
> .../devicetree/bindings/net/mdio-mux.txt | 129 -----------------
> .../devicetree/bindings/net/mdio-mux.yaml | 44 ++++++
> 9 files changed, 340 insertions(+), 406 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/net/mdio-mux-gpio.txt
> create mode 100644 Documentation/devicetree/bindings/net/mdio-mux-gpio.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/mdio-mux-mmioreg.txt
> create mode 100644 Documentation/devicetree/bindings/net/mdio-mux-mmioreg.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/mdio-mux-multiplexer.txt
> create mode 100644 Documentation/devicetree/bindings/net/mdio-mux-multiplexer.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/mdio-mux.txt
> create mode 100644 Documentation/devicetree/bindings/net/mdio-mux.yaml
>
Applied, thanks!
prev parent reply other threads:[~2021-06-01 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 18:14 [PATCH v2] dt-bindings: net: Convert MDIO mux bindings to DT schema Rob Herring
2021-05-26 18:51 ` Andrew Lunn
2021-05-26 20:48 ` Rob Herring
2021-06-01 23:48 ` Rob Herring [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=20210601234855.GA1357013@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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).