From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] dt-bindings: mdio-mux: Add documentation for mdio mux for NSP SoC
Date: Mon, 14 Nov 2016 11:22:01 -0600 [thread overview]
Message-ID: <20161114172201.eitumdrusrb466vq@rob-hp-laptop> (raw)
In-Reply-To: <1478683994-12008-2-git-send-email-yendapally.reddy@broadcom.com>
On Wed, Nov 09, 2016 at 04:33:09AM -0500, Yendapally Reddy Dhananjaya Reddy wrote:
> Add documentation for mdio mux available in Broadcom NSP SoC
>
> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>
> ---
> .../devicetree/bindings/net/brcm,mdio-mux-nsp.txt | 57 ++++++++++++++++++++++
> 1 file changed, 57 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/brcm,mdio-mux-nsp.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-11-14 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 9:33 [PATCH 0/6] USB support for Broadcom NSP SoC Yendapally Reddy Dhananjaya Reddy
2016-11-09 9:33 ` [PATCH 1/6] dt-bindings: mdio-mux: Add documentation for mdio mux for " Yendapally Reddy Dhananjaya Reddy
2016-11-09 14:34 ` Andrew Lunn
2016-11-09 22:23 ` Scott Branden
2016-11-14 17:22 ` Rob Herring [this message]
2016-11-09 9:33 ` [PATCH 2/6] dt-bindings: phy: Add documentation for NSP USB3 PHY Yendapally Reddy Dhananjaya Reddy
2016-11-14 17:23 ` Rob Herring
2016-11-09 9:33 ` [PATCH 3/6] net: mdio-mux: Add MDIO mux driver for NSP SoC Yendapally Reddy Dhananjaya Reddy
2016-11-09 14:45 ` Andrew Lunn
2016-11-09 9:33 ` [PATCH 4/6] net: phy: Initialize mdio clock at probe function Yendapally Reddy Dhananjaya Reddy
2016-11-09 9:33 ` [PATCH 5/6] phy: Add USB3 PHY support for Broadcom NSP SoC Yendapally Reddy Dhananjaya Reddy
2016-11-09 9:33 ` [PATCH 6/6] arm: dts: nsp: Add USB nodes to device tree Yendapally Reddy Dhananjaya Reddy
2016-12-13 2:20 ` [PATCH 0/6] USB support for Broadcom NSP SoC Florian Fainelli
2017-01-16 9:17 ` Kishon Vijay Abraham I
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=20161114172201.eitumdrusrb466vq@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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