From: Dave Jones <davej@suse.de>
To: Tim Sullivan <tsullivan@datawest.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BusLogic build error in 2.5.3
Date: Thu, 31 Jan 2002 19:42:37 +0100 [thread overview]
Message-ID: <20020131194237.B10343@suse.de> (raw)
In-Reply-To: <1012501663.1349.20.camel@prostock.ecom-tech.com>
In-Reply-To: <1012501663.1349.20.camel@prostock.ecom-tech.com>; from tsullivan@datawest.net on Thu, Jan 31, 2002 at 11:27:42AM -0700
On Thu, Jan 31, 2002 at 11:27:42AM -0700, Tim Sullivan wrote:
> According to a note in the scsi_obsolete.c file, "Once the last
> driver uses the new code this *ENTIRE* file will be nuked."
> It seems that scsi_obsolete.c has been "nuked" prematurely :)
Perhaps the was the hope a preemptive nuke would push the
maintainer / someone who cared about the driver to fix it up 8-)
Randy Dunlap's 2.5 page has a list of the steps needed iirc.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-31 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 18:27 BusLogic build error in 2.5.3 Tim Sullivan
2002-01-31 18:42 ` Dave Jones [this message]
2002-01-31 18:53 ` Alan Cox
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=20020131194237.B10343@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tsullivan@datawest.net \
/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