All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Craig Kulesa <ckulesa@as.arizona.edu>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [USB] uhci-hcd oops on APM resume (2.5.23-26)
Date: Sat, 20 Jul 2002 14:36:53 -0400	[thread overview]
Message-ID: <20020720143653.B23737@sventech.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207192306030.5859-100000@loke.as.arizona.edu>; from ckulesa@as.arizona.edu on Fri, Jul 19, 2002 at 11:18:18PM -0700

On Fri, Jul 19, 2002, Craig Kulesa <ckulesa@as.arizona.edu> wrote:
> Excellent.  The patch from Jan Harkes that you posted 
> (http://www.cs.helsinki.fi/linux/linux-kernel/2002-28/1463.html)
> worked wonderfully for me.  No more rogue USB disconnects on APM resume, 
> and no more oopses. 
> 
> Any hopes for sending it Linus-ward? ;)

FWIW Greg, this patch is correct. Thanks!

JE


  reply	other threads:[~2002-07-20 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19  6:28 [USB] uhci-hcd oops on APM resume (2.5.23-26) Craig Kulesa
2002-07-19 19:43 ` Greg KH
2002-07-20  6:18   ` Craig Kulesa
2002-07-20 18:36     ` Johannes Erdfelt [this message]
2002-07-20 19:26       ` 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=20020720143653.B23737@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=ckulesa@as.arizona.edu \
    --cc=greg@kroah.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.