From: "Mads Martin Jørgensen" <mmj@suse.com>
To: Bill Nottingham <notting@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac11
Date: Thu, 17 May 2001 18:59:41 -0700 [thread overview]
Message-ID: <20010517185941.K776@suse.com> (raw)
In-Reply-To: <E150XLO-0006NY-00@the-village.bc.nu> <20010517214700.A15306@nostromo.devel.redhat.com>
In-Reply-To: <20010517214700.A15306@nostromo.devel.redhat.com>; from notting@redhat.com on Thu, May 17, 2001 at 09:47:00PM -0400
* Bill Nottingham <notting@redhat.com> [May 17. 2001 18:55]:
> (catching up...)
>
> Alan Cox (alan@lxorguk.ukuu.org.uk) said:
> > 2.4.4-ac9
> ...
> > o Further tulip updates (Jeff Garzik)
> ...
> > 2.4.4-ac8
> > o Tulip driver updates (Jeff Garzik)
>
> These updates (sorry, haven't tracked down which of the two) conspire to
> break the tulip on my ia64, it's a:
You should try the newest driver from:
http://sourceforge.net/projects/tulip/
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic and
totally illogic, with just a little bit more effort."
-- A. P. J.
prev parent reply other threads:[~2001-05-18 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 23:38 Linux 2.4.4-ac11 Alan Cox
2001-05-18 1:47 ` Bill Nottingham
2001-05-18 1:59 ` Mads Martin Jørgensen [this message]
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=20010517185941.K776@suse.com \
--to=mmj@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.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