From: Jens Axboe <axboe@suse.de>
To: Eric Youngdale <eric@andante.org>
Cc: Jonathan Lahr <lahr@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: io_request_lock patch?
Date: Wed, 11 Jul 2001 10:05:53 +0200 [thread overview]
Message-ID: <20010711100553.D17314@suse.de> (raw)
In-Reply-To: <20010709123936.E6013@us.ibm.com> <20010709214453.U16505@suse.de> <20010710124903.H6013@us.ibm.com> <00a401c1097c$343d45b0$4d0310ac@fairfax.mkssoftware.com>
In-Reply-To: <00a401c1097c$343d45b0$4d0310ac@fairfax.mkssoftware.com>
On Tue, Jul 10 2001, Eric Youngdale wrote:
>
> The bit that I had automated was to essentially fix each and every
> low-level SCSI driver such that each low-level driver would be responsible
> for it's own locking. At this point the patches and the tool are on hold -
> once the 2.5 kernel series gets underway, I can generate some fairly massive
> patchsets.
Cool, sounds good Eric. I'll probably go ahead and complete the initial
ll_rw_blk and IDE work, along with a few selected SCSI drivers. Then
leave the grunt of the work for your tools.
--
Jens Axboe
next prev parent reply other threads:[~2001-07-11 8:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 19:39 io_request_lock patch? Jonathan Lahr
2001-07-09 19:44 ` Jens Axboe
2001-07-10 19:49 ` Jonathan Lahr
2001-07-10 20:09 ` Eric Youngdale
2001-07-11 8:05 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-10 11:55 Dipankar Sarma
2001-07-10 23:05 ` Mike Anderson
2001-07-11 7:15 ` Jens Axboe
2001-07-11 8:53 ` Dipankar Sarma
2001-07-11 8:53 ` Jens Axboe
2001-07-11 14:02 ` Dipankar Sarma
2001-07-11 14:01 ` Jens Axboe
2001-07-11 14:55 ` Dipankar Sarma
2001-07-11 19:16 ` Jens Axboe
2001-07-11 16:02 ` Mike Anderson
2001-07-11 19:20 ` Jens Axboe
2001-07-11 20:13 ` Dipankar Sarma
2001-07-11 20:17 ` Jens Axboe
2001-07-11 21:05 ` Mike Anderson
2001-07-11 7:19 ` Jens Axboe
2001-07-11 8:39 ` Dipankar Sarma
2001-07-11 8:47 ` Jens Axboe
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=20010711100553.D17314@suse.de \
--to=axboe@suse.de \
--cc=eric@andante.org \
--cc=lahr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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