mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: rberg@berg-solutions.de
Cc: andrew@lunn.ch, bryan.whitehead@microchip.com,
	UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lan743x: Added fixed link and RGMII support
Date: Mon, 01 Jun 2020 11:51:36 -0700 (PDT)	[thread overview]
Message-ID: <20200601.115136.1314501977250032604.davem@davemloft.net> (raw)
In-Reply-To: <20200529193003.3717-1-rberg@berg-solutions.de>

From: Roelof Berg <rberg@berg-solutions.de>
Date: Fri, 29 May 2020 21:30:02 +0200

> Microchip lan7431 is frequently connected to a phy. However, it
> can also be directly connected to a MII remote peer without
> any phy in between. For supporting such a phyless hardware setup
> in Linux we utilized phylib, which supports a fixed-link
> configuration via the device tree. And we added support for
> defining the connection type R/GMII in the device tree.
 ...

Applied, thank you.

  parent reply	other threads:[~2020-06-01 18:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 19:30 Roelof Berg
2020-05-29 21:30 ` Andrew Lunn
2020-06-01 18:51 ` David Miller [this message]
2020-06-03 14:52   ` [PATCH] lan743x: Added fixed link and RGMII support / BROKEN PATCH Roelof Berg
2020-06-03 15:59     ` Andrew Lunn
2020-06-03 16:33       ` [PATCH] lan743x: Added fixed link and RGMII support / debugging Roelof Berg
2020-06-03 18:06         ` Andrew Lunn
2020-06-03 18:31           ` Roelof Berg
2020-06-03 22:02           ` Roelof Berg
2020-06-03 16:36       ` Roelof Berg
2020-06-03 18:02         ` Andrew Lunn
     [not found] ` <08FC216E-BBCA-40E6-8251-FA1EB3EF9F99@berg-solutions.de>
2020-06-03 15:10   ` [PATCH] lan743x: Added fixed link and RGMII support / Options for proceeding ? Roelof Berg

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=20200601.115136.1314501977250032604.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=bryan.whitehead@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rberg@berg-solutions.de \
    /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®