From: Greg KH <greg@kroah.com>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: Craig Kulesa <ckulesa@as.arizona.edu>, linux-kernel@vger.kernel.org
Subject: Re: [USB] uhci-hcd oops on APM resume (2.5.23-26)
Date: Sat, 20 Jul 2002 12:26:59 -0700 [thread overview]
Message-ID: <20020720192659.GA27715@kroah.com> (raw)
In-Reply-To: <20020720143653.B23737@sventech.com>
On Sat, Jul 20, 2002 at 02:36:53PM -0400, Johannes Erdfelt wrote:
> 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!
Great, I'll send it off in the next round of patches. Craig, thanks for
testing it out.
greg k-h
prev parent reply other threads:[~2002-07-20 19:25 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
2002-07-20 19:26 ` Greg KH [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=20020720192659.GA27715@kroah.com \
--to=greg@kroah.com \
--cc=ckulesa@as.arizona.edu \
--cc=johannes@erdfelt.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