From: Andreas Dilger <adilger@turbolabs.com>
To: Christoph Hellwig <hch@caldera.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre2 does not compile
Date: Wed, 28 Nov 2001 09:26:00 -0700 [thread overview]
Message-ID: <20011128092600.Q730@lynx.no> (raw)
In-Reply-To: <200111272209.fARM9tk18991@ns.caldera.de> <Pine.LNX.4.33.0111271628430.1629-100000@penguin.transmeta.com> <20011128135508.A21418@caldera.de>
In-Reply-To: <20011128135508.A21418@caldera.de>; from hch@caldera.de on Wed, Nov 28, 2001 at 01:55:08PM +0100
On Nov 28, 2001 13:55 +0100, Christoph Hellwig wrote:
> > > While we are at breaking scsi, would you take a patch to remove the
> > > old-style (2.0) scsi error handling completly, forcing drivers still
> > > using it to be fixed? Early 2.5 looks like a good time for that to me..
>
> --- ../master/linux-2.5.1-pre2/drivers/scsi/aic7xxx_old/aic7xxx.h Sun Mar 4 23:30:18 2001
> +++ linux/drivers/scsi/aic7xxx_old/aic7xxx.h Wed Nov 28 13:35:21 2001
> @@ -55,7 +55,6 @@
> present: 0, /* number of 7xxx's present */\
> unchecked_isa_dma: 0, /* no memory DMA restrictions */\
> use_clustering: ENABLE_CLUSTERING, \
> - use_new_eh_code: 0 \
> }
>
> extern int aic7xxx_queue(Scsi_Cmnd *, void (*)(Scsi_Cmnd *));
What would be nice in the case of drivers that don't use the new error
handling code is to add something like:
#warning "Uses obsolete SCSI error code, see Documentation/2.5/scsi-error.txt"
for a hint as to the reason why it no longer compiles, and a short guide
on how to update the drivers.
The same would be good for Jens' changes - his document could be put into
2.5/bio.txt or something, so any currently out-of-kernel coders can find it.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-28 16:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 20:44 2.5.1-pre2 does not compile f5ibh
2001-11-27 20:50 ` Linus Torvalds
2001-11-27 22:02 ` Paul Mackerras
2001-11-28 1:04 ` Linus Torvalds
2001-11-28 1:34 ` Block I/O Enchancements, 2.5.1-pre2 Jeff V. Merkey
2001-11-28 1:45 ` Jeff Garzik
2001-11-28 1:55 ` Jeff V. Merkey
2001-11-28 2:32 ` Jeff Garzik
2001-11-28 3:38 ` Linus Torvalds
2001-11-30 2:19 ` Daniel Phillips
2001-11-30 12:21 ` Hans Reiser
[not found] ` <15367.32910.275973.287742@laputa.namesys.com>
2001-12-01 9:31 ` [reiserfs-dev] " Hans Reiser
2001-11-28 10:17 ` Martin Dalecki
2001-11-28 13:35 ` Jens Axboe
2001-11-28 17:29 ` Jeff Merkey
2001-11-28 6:58 ` 2.5.1-pre2 does not compile Jens Axboe
2001-11-28 12:20 ` bio write-up (was: Re: 2.5.1-pre2 does not compile) Jens Axboe
2001-11-28 23:31 ` 2.5.1-pre2 bio offset by one error in VIA IDE Anton Altaparmakov
2001-11-28 23:55 ` Andreas Dilger
2001-11-29 1:07 ` Anton Altaparmakov
2001-11-30 1:53 ` 2.5.1-pre2 does not compile Daniel Phillips
2001-11-27 22:09 ` Christoph Hellwig
2001-11-27 22:22 ` onboard ethernet/sound on Soyo SY-K7V? Dax Kelson
2001-11-27 22:47 ` François Cami
2001-11-27 22:57 ` Jeff Garzik
2001-11-27 22:29 ` 2.5.1-pre2 does not compile Robert Love
2001-11-28 0:29 ` Linus Torvalds
2001-11-28 12:55 ` Christoph Hellwig
2001-11-28 16:26 ` Andreas Dilger [this message]
2001-11-28 16:42 ` Christoph Hellwig
2001-11-28 16:39 ` Martin Dalecki
2001-11-28 17:27 ` Andreas Dilger
2001-11-28 0:40 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 21:02 Wayne.Brown
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=20011128092600.Q730@lynx.no \
--to=adilger@turbolabs.com \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
/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