From: Christoph Hellwig <hch@infradead.org>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Arjan van de Ven <arjan@infradead.org>,
"Bagalkote, Sreenivas" <sreenib@lsil.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt_Domsch@Dell.com, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 2.6.12-rc4-mm1 3/4] megaraid_sas: updating the driver
Date: Wed, 25 May 2005 06:49:14 +0100 [thread overview]
Message-ID: <20050525054914.GA8574@infradead.org> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458B01399B22@otce2k01.adaptec.com>
On Tue, May 24, 2005 at 04:45:05PM -0400, Salyzyn, Mark wrote:
> Could I get an historical (2.4 & Distribution) perspective on this. At
> which point, or what code/include/manifest/version delineating it, would
> you say the driver is no longer, if ever, required to place a lock
> (host_lock or io_request_lock) around the scsi_done call?
>
> I expect (or hope) the answer to be: always needs io_request_lock in
> 2.4, never needed the host_lock in 2.5+.
You don't need any lock in 2.4 either.
next prev parent reply other threads:[~2005-05-25 5:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 20:45 [PATCH 2.6.12-rc4-mm1 3/4] megaraid_sas: updating the driver Salyzyn, Mark
2005-05-24 21:16 ` Arjan van de Ven
2005-05-25 5:49 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-17 23:51 Bagalkote, Sreenivas
2005-05-18 13:53 ` 'Christoph Hellwig'
2005-05-17 22:13 Bagalkote, Sreenivas
2005-05-16 6:57 Bagalkote, Sreenivas
2005-05-16 8:06 ` Arjan van de Ven
2005-05-16 14:18 ` James Bottomley
2005-05-16 14:24 ` Arjan van de Ven
2005-05-16 14:50 ` 'Christoph Hellwig'
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=20050525054914.GA8574@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=Matt_Domsch@Dell.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=sreenib@lsil.com \
/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