From: Tim Waugh <twaugh@redhat.com>
To: John Cavan <johncavan@home.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0test11ac4
Date: Sun, 26 Nov 2000 16:40:58 +0000 [thread overview]
Message-ID: <20001126164058.B23819@redhat.com> (raw)
In-Reply-To: <E13zmwU-0001MJ-00@the-village.bc.nu> <3A203F0A.29336B56@home.com>
In-Reply-To: <3A203F0A.29336B56@home.com>; from johncavan@home.com on Sat, Nov 25, 2000 at 05:36:58PM -0500
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
On Sat, Nov 25, 2000 at 05:36:58PM -0500, John Cavan wrote:
> Just so I understand the differences, for learning purposes... Tim
> did this a little different than I did and I'd just like to
> understand the "whys" of it.
It's Douglas Gilbert's modified patch; Douglas explained that he
didn't find that dropping the io_request_lock for just
parport_enumerate was enough during his testing.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2000-11-26 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-25 21:33 Linux 2.4.0test11ac4 Alan Cox
2000-11-25 22:36 ` John Cavan
2000-11-26 16:40 ` Tim Waugh [this message]
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=20001126164058.B23819@redhat.com \
--to=twaugh@redhat.com \
--cc=johncavan@home.com \
--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