From: 'Christoph Hellwig' <hch@infradead.org>
To: "Mukker, Atul" <atulm@lsil.com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
"'linux-megaraid-devel@dell.com'" <linux-megaraid-devel@dell.com>
Subject: Re: [ANNOUNCE] megaraid linux driver version 2.00.7
Date: Wed, 6 Aug 2003 06:43:53 +0100 [thread overview]
Message-ID: <20030806064353.A21769@infradead.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570185F3FA@EXA-ATLANTA.se.lsil.com>; from atulm@lsil.com on Tue, Aug 05, 2003 at 06:09:10PM -0400
On Tue, Aug 05, 2003 at 06:09:10PM -0400, Mukker, Atul wrote:
> > + spin_lock_irqsave(adapter->host->host_lock, flags);
> But all kernels do not have this lock as part of the host structure. With
> 2.00.7, I have relapsed a patch which switches the lock to io_request_lock
> if kernel does not support per host lock.
>
> And not all kernels have the per host lock named as "host->host_lock", some
> simply have "host->lock"A
All 2.5/2.6 kernels do have host->host_lock and the 2.5 driver is different
from the 2.4 one. In fact it will hopefuloly become &host->host_lock soon
but for that I have to repair the remaining abusers first.
next prev parent reply other threads:[~2003-08-06 5:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 22:09 [ANNOUNCE] megaraid linux driver version 2.00.7 Mukker, Atul
2003-08-06 5:43 ` 'Christoph Hellwig' [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-06 13:05 Mukker, Atul
2003-08-04 18:18 Mukker, Atul
2003-08-04 20:47 ` 'Christoph Hellwig'
2003-08-02 4:59 haruo tomita
2003-08-01 21:56 Mukker, Atul
2003-08-02 9:16 ` Christoph Hellwig
2003-08-01 20:39 Mukker, Atul
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=20030806064353.A21769@infradead.org \
--to=hch@infradead.org \
--cc=atulm@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-megaraid-devel@dell.com \
--cc=linux-scsi@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