* ether509.c.diff problem
@ 1995-08-22 21:49 Scott
0 siblings, 0 replies; 2+ messages in thread
From: Scott @ 1995-08-22 21:49 UTC (permalink / raw)
Is the diff for ether509.c correct? It looks like some of the changes
there have already been applied to the code on the cdrom. Can we get a
clean diff from cdrom to current?
^ permalink raw reply [flat|nested] 2+ messages in thread
* ether509.c.diff problem
@ 1995-08-23 1:13 jmk
0 siblings, 0 replies; 2+ messages in thread
From: jmk @ 1995-08-23 1:13 UTC (permalink / raw)
It looks like the diff was completely bogus to me. I've replaced it with just a
copy of the complete interrupt routine.
A diff on the current source would be too much, there's code for the 3C590 which
would mean pulling in the PCI support file, etc.
------ original message follows ------
>From cse.psu.edu!9fans-outgoing-owner Tue Aug 22 18:26:46 EDT 1995
Received: by colossus.cse.psu.edu id <45512>; Tue, 22 Aug 1995 18:11:13 -0400
Received: from galapagos.cse.psu.edu ([130.203.2.12]) by colossus.cse.psu.edu with SMTP id <45610>; Tue, 22 Aug 1995 17:59:27 -0400
Received: by galapagos.cse.psu.edu id <12728>; Tue, 22 Aug 1995 17:50:01 -0400
From: Scott Schwartz <schwartz@galapagos.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: ether509.c.diff problem
Message-Id: <95Aug22.175001edt.12728@galapagos.cse.psu.edu>
Date: Tue, 22 Aug 1995 17:49:57 -0400
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
Is the diff for ether509.c correct? It looks like some of the changes
there have already been applied to the code on the cdrom. Can we get a
clean diff from cdrom to current?
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1995-08-23 1:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1995-08-22 21:49 ether509.c.diff problem Scott
1995-08-23 1:13 jmk
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).