From: jmk@plan9.att.com jmk@plan9.att.com
Subject: ether509.c.diff problem
Date: Tue, 22 Aug 1995 21:13:17 -0400 [thread overview]
Message-ID: <19950823011317.pPBRpd_Z5rqqzoZJ9OAW-XQHoaBWJ7RnxcFwkltEa4c@z> (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?
next reply other threads:[~1995-08-23 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-23 1:13 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-22 21:49 Scott
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=19950823011317.pPBRpd_Z5rqqzoZJ9OAW-XQHoaBWJ7RnxcFwkltEa4c@z \
--to=jmk@plan9.att.com \
/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).