mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Moritz Fischer <moritz.fischer@ettus.com>
To: netdev@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	alex.williams@ni.com, andrew@lunn.ch, robh+dt@kernel.org,
	davem@davemloft.net, moritz.fischer@ettus.com,
	Moritz Fischer <mdf@kernel.org>
Subject: [PATCH net-next 0/3] nixge: Fixed-link support
Date: Mon,  4 Feb 2019 09:30:37 -0800	[thread overview]
Message-ID: <20190204173040.5538-1-moritz.fischer@ettus.com> (raw)

From: Moritz Fischer <mdf@kernel.org>

This series adds fixed-link support to nixge.

The first patch corrects the binding to correctly reflect
hardware that does not come with MDIO cores instantiated.

The second patch adds fixed link support to the driver.

The third patch updates the binding document with the now
optional (formerly required) phy-handle property and references
the fixed-link docs.

Thanks,
Moritz

Moritz Fischer (3):
  net: nixge: Make mdio child node optional
  net: nixge: Add support for fixed-link configurations
  dt-bindings: net: Add fixed-link support

 .../devicetree/bindings/net/nixge.txt         | 60 +++++++++++++++++--
 drivers/net/ethernet/ni/nixge.c               | 44 ++++++++++----
 2 files changed, 88 insertions(+), 16 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-02-04 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 17:30 Moritz Fischer [this message]
2019-02-04 17:30 ` [PATCH net-next 1/3] net: nixge: Make mdio child node optional Moritz Fischer
2019-02-04 17:30 ` [PATCH net-next 2/3] net: nixge: Add support for fixed-link configurations Moritz Fischer
2019-02-04 17:30 ` [PATCH net-next 3/3] dt-bindings: net: Add fixed-link support Moritz Fischer
2019-02-05 18:34 ` [PATCH net-next 0/3] nixge: Fixed-link support David Miller
  -- strict thread matches above, loose matches on Subject: below --
2018-08-30  0:40 [PATCH net-next 0/3] nixge: fixed-link support Moritz Fischer

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=20190204173040.5538-1-moritz.fischer@ettus.com \
    --to=moritz.fischer@ettus.com \
    --cc=alex.williams@ni.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --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

all inboxes | Powered by JetHome®