From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH net-next v3 0/3] dt-bindings: net: mdio.yaml fixes
Date: Mon, 20 Apr 2020 11:07:20 -0700 [thread overview]
Message-ID: <20200420180723.27936-1-f.fainelli@gmail.com> (raw)
Hi,
This patch series documents some common MDIO devices properties such as
resets (and delays) and broken-turn-around. The second patch also
rephrases some descriptions to be more general towards MDIO devices and
not specific towards Ethernet PHYs.
Changes in v3:
- corrected wording of 'broken-turn-around' in ethernet-phy.yaml and
mdio.yaml, add Andrew's R-b tag to patch #3
Florian Fainelli (3):
dt-bindings: net: Correct description of 'broken-turn-around'
dt-bindings: net: mdio: Document common properties
dt-bindings: net: mdio: Make descriptions more general
.../devicetree/bindings/net/ethernet-phy.yaml | 3 +-
.../devicetree/bindings/net/mdio.yaml | 38 ++++++++++++++++---
2 files changed, 35 insertions(+), 6 deletions(-)
--
2.19.1
next reply other threads:[~2020-04-20 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 18:07 Florian Fainelli [this message]
2020-04-20 18:07 ` [PATCH net-next v3 1/3] dt-bindings: net: Correct description of 'broken-turn-around' Florian Fainelli
2020-04-20 19:58 ` Andrew Lunn
2020-04-20 18:07 ` [PATCH net-next v3 2/3] dt-bindings: net: mdio: Document common properties Florian Fainelli
2020-04-20 19:59 ` Andrew Lunn
2020-04-20 18:07 ` [PATCH net-next v3 3/3] dt-bindings: net: mdio: Make descriptions more general Florian Fainelli
2020-04-22 18:43 ` [PATCH net-next v3 0/3] dt-bindings: net: mdio.yaml fixes David Miller
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=20200420180723.27936-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.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).