netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave.anglin@bell.net>,
	Arlie Davis <arlied@google.com>, Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: Bug report (with fix) for DEC Tulip driver (de2104x.c)
Date: Wed, 18 Sep 2019 07:56:16 +0200	[thread overview]
Message-ID: <f71e9773-5cfb-f20b-956f-d98b11a5d4a7@gmx.de> (raw)
In-Reply-To: <df0f961d-2d53-63e3-8087-6f0b09e14317@bell.net>

On 18.09.19 00:51, John David Anglin wrote:
> On 2019-09-17 5:36 p.m., Arlie Davis wrote:
>> Likewise, I'm at a loss for testing with real hardware. It's hard to
>> find such things, now.
> How does de2104x compare to ds2142/43?  I have a c3750 with ds2142/43 tulip.  Helge
> or some others might have a machine with a de2104x.

The machines we could test are
* a C240 with a DS21140 tulip chip (Sven has one),
* a C3000 or similiar with DS21142 and/or DS21143 (me).

If the patch does not show any regressions, I'd suggest to
apply it upstream.

Helge

  reply	other threads:[~2019-09-18  5:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 21:50 Bug report (with fix) for DEC Tulip driver (de2104x.c) Arlie Davis
2019-09-17 21:28 ` Andrew Lunn
2019-09-17 21:36   ` Arlie Davis
2019-09-17 22:51     ` John David Anglin
2019-09-18  5:56       ` Helge Deller [this message]
2019-09-18 13:27         ` Thomas Bogendoerfer
2019-10-03  1:29           ` Maciej W. Rozycki
2019-09-19 20:31         ` Sven Schnelle
2019-09-20 10:43 ` Thomas Bogendoerfer

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=f71e9773-5cfb-f20b-956f-d98b11a5d4a7@gmx.de \
    --to=deller@gmx.de \
    --cc=andrew@lunn.ch \
    --cc=arlied@google.com \
    --cc=dave.anglin@bell.net \
    --cc=linux-parisc@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).