From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, Michael Walle <michael@walle.cc>
Subject: Re: [PATCH 2/5] dt-bindings: net: phy: Add support for AT803X
Date: Tue, 5 Nov 2019 22:37:25 -0600 [thread overview]
Message-ID: <20191106043725.GA22549@bogus> (raw)
In-Reply-To: <20191102011351.6467-3-michael@walle.cc>
On Sat, 2 Nov 2019 02:13:48 +0100, Michael Walle wrote:
> Document the Atheros AR803x PHY bindings.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> .../devicetree/bindings/net/qca,ar803x.yaml | 111 ++++++++++++++++++
> MAINTAINERS | 2 +
> include/dt-bindings/net/qca-ar803x.h | 13 ++
> 3 files changed, 126 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/qca,ar803x.yaml
> create mode 100644 include/dt-bindings/net/qca-ar803x.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-11-06 4:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 1:13 [PATCH 0/5] net: phy: at803x device tree binding Michael Walle
2019-11-02 1:13 ` [PATCH 1/5] net: phy: at803x: fix Kconfig description Michael Walle
2019-11-02 2:57 ` Florian Fainelli
2019-11-02 1:13 ` [PATCH 2/5] dt-bindings: net: phy: Add support for AT803X Michael Walle
2019-11-02 2:59 ` Florian Fainelli
2019-11-06 4:37 ` Rob Herring [this message]
2019-11-02 1:13 ` [PATCH 3/5] net: phy: at803x: add device tree binding Michael Walle
2019-11-02 3:01 ` Florian Fainelli
2019-11-05 22:28 ` Michael Walle
2019-11-02 1:13 ` [PATCH 4/5] net: phy: at803x: mention AR8033 as same as AR8031 Michael Walle
2019-11-02 1:13 ` [PATCH 5/5] net: phy: at803x: fix the PHY names Michael Walle
2019-11-02 3:21 ` Florian Fainelli
2019-11-05 22:06 ` [PATCH 0/5] net: phy: at803x device tree binding David Miller
2019-11-05 22:22 ` Michael Walle
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=20191106043725.GA22549@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.