All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Roelof Berg <rberg@berg-solutions.de>
Cc: David Miller <davem@davemloft.net>,
	Bryan Whitehead <bryan.whitehead@microchip.com>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lan743x: Added fixed link and RGMII support / BROKEN PATCH
Date: Wed, 3 Jun 2020 17:59:27 +0200	[thread overview]
Message-ID: <20200603155927.GC869823@lunn.ch> (raw)
In-Reply-To: <D784BC1B-D14C-4FE4-8FD8-76BEBE60A39D@berg-solutions.de>

On Wed, Jun 03, 2020 at 04:52:32PM +0200, Roelof Berg wrote:
> TEST REPORT: BROKEN PATCH
> 
> Thanks to everyone for working on the fixed link feature of lan743x eth driver.
> 

> I received more test hardware today, and one piece of hardware
> (EVBlan7430) becomes incompatible by the patch. We need to roll back
> for now. Sorry.

Hi Roelof

We have a bit of time to fix this, before it becomes too critical.
So lets try to fix it.

How did it break?

    Thanks
	Andrew

  reply	other threads:[~2020-06-03 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 19:30 [PATCH] lan743x: Added fixed link and RGMII support Roelof Berg
2020-05-29 21:30 ` Andrew Lunn
2020-06-01 18:51 ` David Miller
2020-06-03 14:52   ` [PATCH] lan743x: Added fixed link and RGMII support / BROKEN PATCH Roelof Berg
2020-06-03 15:59     ` Andrew Lunn [this message]
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=20200603155927.GC869823@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --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 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.