From: Mark Lord <lkml@rtr.ca>
To: Greg KH <gregkh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] USB patches for 2.6.13
Date: Thu, 08 Sep 2005 22:41:37 -0400 [thread overview]
Message-ID: <4320F661.2010706@rtr.ca> (raw)
In-Reply-To: <20050908235024.GA8159@kroah.com>
Is someone actively working on USB Suspend/Resume support yet?
I ask because this is becoming more and more important as people
shift more to portable notebook computers with Linux.
Enabling CONFIG_USB_SUSPEND is currently a surefire way to
guarantee crashing my own notebook on suspend/resume,
whereas it *usually* (but not always) survives when that
config option is left unset.
Nothing complicated in the configuration -- just a USB mouse,
but that's enough to nuke it.
Anyone looking at that stuff right now?
next prev parent reply other threads:[~2005-09-09 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 23:50 [GIT PATCH] USB patches for 2.6.13 Greg KH
2005-09-09 2:41 ` Mark Lord [this message]
2005-09-09 3:27 ` [linux-usb-devel] " David Brownell
2005-09-09 3:28 ` 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=4320F661.2010706@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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