From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: "Paulo Andre'" <l16083@alunos.uevora.pt>
Cc: linux-kernel@vger.kernel.org, "Jens Axboe" <axboe@suse.de>
Subject: Re: Can't compile Symbios 53c416 SCSI support
Date: Mon, 28 Jan 2002 04:38:33 +0300 [thread overview]
Message-ID: <20020128043833.659e7102.johnpol@2ka.mipt.ru> (raw)
In-Reply-To: <20020127201213.A7091@bleach>
In-Reply-To: <20020127201213.A7091@bleach>
On Sun, 27 Jan 2002 20:12:13 +0000
"Paulo Andre'" <l16083@alunos.uevora.pt> wrote:
> sym53c416.c: In function `sym53c416_intr_handle':
> sym53c416.c:362: `io_request_lock' undeclared (first use in this
> function)
> sym53c416.c:362: (Each undeclared identifier is reported only once
> sym53c416.c:362: for each function it appears in.)
> I'm a newbie though I see <linux/blk.h> is included. Still it says
> io_request_lock is undeclared... should be trivial but goes beyond my
> knowledge :)
It seems that io_request_lock will be completely removed in 2.5 tree, so
there is no io_request_lock in linux/blk.h. This global lock now exsist
only in scsi layer, and it will be replaced by Scsi_Host->host_lock soon.
So i hope this patch will help a bit in this direction.
2 Paulo Andre: DON'T use this patch before Jens Axboe will agree with it,
because i even haven't scsi here, so this patch was written only with
common sence. I hope this will help you.
>
> Thanks in advance
>
> // Paulo Andre'
Evgeniy Polyakov ( s0mbre ).
next prev parent reply other threads:[~2002-01-28 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 20:12 Can't compile Symbios 53c416 SCSI support Paulo Andre'
2002-01-28 1:38 ` Evgeniy Polyakov [this message]
2002-01-28 1:41 ` Evgeniy Polyakov
2002-01-28 1:58 ` Paulo Andre'
2002-01-28 1:54 ` Paulo Andre'
-- strict thread matches above, loose matches on Subject: below --
2002-01-28 4:58 Douglas Gilbert
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=20020128043833.659e7102.johnpol@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=axboe@suse.de \
--cc=l16083@alunos.uevora.pt \
--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