From: Pavel Machek <pavel@ucw.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux PM <linux-pm@osdl.org>
Subject: Re: Re: [RFC][PATCH] swsusp: warn about USB devices in documentation
Date: Mon, 20 Feb 2006 21:41:05 +0100 [thread overview]
Message-ID: <20060220204105.GC21557@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0602201526330.28136-100000@netrider.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Po 20-02-06 15:30:16, Alan Stern wrote:
> On Mon, 20 Feb 2006, Patrick Mochel wrote:
>
> > > And if the computer can wake up in response to USB events, then obviously
> > > the USB controller _is_ receiving some power.
> >
> > True, and I apologize if I misunderstood your initial question. By "up", I
> > thought you meant fully powered and functional.
>
> No; in the context of this thread I merely meant suspend-power was
> present. Pavel had said that a machine which supplies any USB power at
> all during swsusp is broken. I was trying to show this isn't so.
I take that back. I still claim it is unusal ;-).
Pavel
--
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-02-20 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 22:06 [RFC][PATCH] swsusp: warn about USB devices in documentation Rafael J. Wysocki
2006-02-19 22:13 ` Pavel Machek
2006-02-20 3:50 ` Alan Stern
2006-02-20 10:34 ` Pavel Machek
2006-02-20 13:23 ` Rafael J. Wysocki
2006-02-20 15:34 ` Alan Stern
2006-02-20 16:37 ` Pavel Machek
2006-02-20 16:41 ` Alan Stern
2006-02-20 16:43 ` Pavel Machek
2006-02-20 18:23 ` Patrick Mochel
2006-02-20 19:45 ` Alan Stern
2006-02-20 20:13 ` Patrick Mochel
2006-02-20 20:30 ` Alan Stern
2006-02-20 20:41 ` Pavel Machek [this message]
2006-02-20 10:36 ` Rafael J. Wysocki
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=20060220204105.GC21557@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-pm@osdl.org \
--cc=stern@rowland.harvard.edu \
/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.