Re: kern/37963 (fxp0: device timeout)

[Brian Havens <bchavens%gmail.com@localhost>]

The following reply was made to PR kern/37963; it has been noted by GNATS.

From: Brian Havens <bchavens%gmail.com@localhost>
To: "gnats-bugs%netbsd.org@localhost" <gnats-bugs%netbsd.org@localhost>
Cc: "kern-bug-people%netbsd.org@localhost" <kern-bug-people%netbsd.org@localhost>, 
	"netbsd-bugs%netbsd.org@localhost" <netbsd-bugs%netbsd.org@localhost>, "gnats-admin%netbsd.org@localhost" <gnats-admin%netbsd.org@localhost>, 
	"dholland%netbsd.org@localhost" <dholland%netbsd.org@localhost>
Subject: Re: kern/37963 (fxp0: device timeout)
Date: Sun, 31 Jul 2016 17:32:08 -0400

 --94eb2c1252904c97770538f537c3
 Content-Type: text/plain; charset=UTF-8
 
 Unfortunately, that was submitted in 2008 and the hardware is long gone.
 Thanks for going through and cleaning these open bug reports up though.
 
 On Sunday, July 31, 2016, <dholland%netbsd.org@localhost> wrote:
 
 > Synopsis: fxp0: device timeout
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: dholland%NetBSD.org@localhost
 > State-Changed-When: Sun, 31 Jul 2016 21:01:35 +0000
 > State-Changed-Why:
 > sigh, another PR that nobody ever answered.
 >
 > do you still have this hardware and is it still broken?
 >
 >
 >
 >
 
 --94eb2c1252904c97770538f537c3
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 Unfortunately, that was submitted in 2008 and the hardware is long gone. Th=
 anks for going through and cleaning these open bug reports=C2=A0up though.=
 =C2=A0<br><br>On Sunday, July 31, 2016,  &lt;<a href=3D"mailto:dholland@net=
 bsd.org">dholland%netbsd.org@localhost</a>&gt; wrote:<br><blockquote class=3D"gmail_q=
 uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
 x">Synopsis: fxp0: device timeout<br>
 <br>
 State-Changed-From-To: open-&gt;feedback<br>
 State-Changed-By: dholland%NetBSD.org@localhost<br>
 State-Changed-When: Sun, 31 Jul 2016 21:01:35 +0000<br>
 State-Changed-Why:<br>
 sigh, another PR that nobody ever answered.<br>
 <br>
 do you still have this hardware and is it still broken?<br>
 <br>
 <br>
 <br>
 </blockquote>
 
 --94eb2c1252904c97770538f537c3--