public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: USB deadlock in v2.5.67
Date: Fri, 18 Apr 2003 18:16:09 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705567@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705560@msgid-missing>

>>>>> On Fri, 18 Apr 2003 08:46:56 -0700, David Brownell <david-b@pacbell.net> said:

  David> Seems to be a different problem.  The patch below should
  David> resolve the keyboard problem -- just reorders two lines so
  David> the lock isn't held after the device's records get deleted,
  David> so the order is what it should always have been.

With the patch applied, I can now add/remove USB keyboards without
crashing the kernel.

Thanks!

	--david



  parent reply	other threads:[~2003-04-18 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18  4:50 [Linux-ia64] Re: USB deadlock in v2.5.67 Greg KH
2003-04-18 15:46 ` David Brownell
2003-04-18 18:16 ` David Mosberger [this message]
2003-04-18 23:19 ` Greg KH

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=marc-linux-ia64-105590723705567@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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