From: Tim Waugh <twaugh@redhat.com>
To: John Cavan <johncavan@home.com>
Cc: Jens Axboe <axboe@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] (new for ppa and imm) Re: [PATCH] Re: Patch to fix lockup on ppa insert
Date: Fri, 17 Nov 2000 10:24:11 +0000 [thread overview]
Message-ID: <20001117102411.S6735@redhat.com> (raw)
In-Reply-To: <3A13D4BA.AD4A580B@home.com> <3A13D8D6.8C12E31A@home.com> <20001116162027.C597@suse.de> <3A149D00.9D38FA24@home.com>
In-Reply-To: <3A149D00.9D38FA24@home.com>; from johncavan@home.com on Thu, Nov 16, 2000 at 09:50:40PM -0500
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
On Thu, Nov 16, 2000 at 09:50:40PM -0500, John Cavan wrote:
> [...] This patch unlocks, allows the lowlevel driver to do it's
> probes, and then relocks. It could probably be more granular in the
> parport_pc code, but my own home tests show it to be working fine.
Is that safe?
Also, what bit of the parport code is tripping over the lock?
Request_module or something?
A nicer fix would probably be to use parport_register_driver, but
that's likely to be too big a change right now.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-11-17 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 12:36 Patch to fix lockup on ppa insert John Cavan
2000-11-16 12:53 ` [PATCH] " John Cavan
2000-11-16 15:20 ` Jens Axboe
2000-11-17 2:50 ` [PATCH] (new for ppa and imm) " John Cavan
2000-11-17 10:24 ` Tim Waugh [this message]
2000-11-18 22:10 ` John Cavan
2000-11-20 12:51 ` Tim Waugh
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=20001117102411.S6735@redhat.com \
--to=twaugh@redhat.com \
--cc=axboe@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.