public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Christoph Hellwig <hch@caldera.de>
Cc: Andreas Dilger <adilger@turbolabs.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre2 does not compile
Date: Wed, 28 Nov 2001 17:39:33 +0100	[thread overview]
Message-ID: <3C051345.41D81A1C@evision-ventures.com> (raw)
In-Reply-To: <200111272209.fARM9tk18991@ns.caldera.de> <Pine.LNX.4.33.0111271628430.1629-100000@penguin.transmeta.com> <20011128135508.A21418@caldera.de> <20011128092600.Q730@lynx.no> <20011128174250.A17582@caldera.de>

Christoph Hellwig wrote:
> 
> On Wed, Nov 28, 2001 at 09:26:00AM -0700, Andreas Dilger wrote:
> > 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.
> 
> I already thought about that - as the old error handling code is selected
> by setting a member in a struct to '1' I don't see any easy way to do so...
> 
>         Christoph

Please note that this selection is static with regard to the driver.
It only happens in the initialization code for the driver!
The #warning doesn't have to at the same place where the filed in
the struct was.

  reply	other threads:[~2001-11-28 16:49 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
2001-11-28 16:42           ` Christoph Hellwig
2001-11-28 16:39             ` Martin Dalecki [this message]
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=3C051345.41D81A1C@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=adilger@turbolabs.com \
    --cc=dalecki@evision.ag \
    --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