From: Pavel Machek <pavel@ucw.cz>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Kyle Moffett <mrmacman_g4@mac.com>,
Alon Bar-Lev <alon.barlev@gmail.com>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Flames over -- Re: Which is simpler?
Date: Sun, 19 Feb 2006 20:43:44 +0100 [thread overview]
Message-ID: <20060219194343.GA15311@elf.ucw.cz> (raw)
In-Reply-To: <43F8C464.3000509@cfl.rr.com>
> >since there's no difference (as far as the kernel can see) between power
> >loss on the bus and an actual unplug, you can hardly say that one should
> >be allowed and the other not.
>
> But there _IS_ a difference between power loss and actual unplug, so
> I very well can say one is allowed and the other is not. The fact that
> the kernel can not tell the difference is simply a limitation that must
> be dealt with.
Kernel can not tell the diference, and just because you don't like the
behaviour does not mean we have to work around hardware limitation.
You deal with it. Post a patch.
Pavel
--
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...
next prev parent reply other threads:[~2006-02-19 19:44 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 16:57 Flames over -- Re: Which is simpler? Alan Stern
2006-02-13 0:51 ` Phillip Susi
2006-02-13 2:19 ` Alan Stern
2006-02-13 3:52 ` Phillip Susi
2006-02-13 5:43 ` Kyle Moffett
2006-02-13 16:40 ` Phillip Susi
2006-02-13 16:31 ` Alan Stern
2006-02-13 17:14 ` Phillip Susi
2006-02-13 20:04 ` Alan Stern
2006-02-13 20:38 ` Phillip Susi
2006-02-13 21:24 ` Alan Stern
2006-02-13 22:27 ` Rafael J. Wysocki
2006-02-14 19:26 ` Alan Stern
2006-02-14 20:41 ` Rafael J. Wysocki
2006-02-14 21:08 ` Lee Revell
2006-02-15 15:56 ` Alan Stern
2006-02-13 22:51 ` J. Bruce Fields
2006-02-13 23:47 ` Phillip Susi
2006-02-14 0:50 ` Kyle Moffett
2006-02-14 2:09 ` Phillip Susi
2006-02-14 4:09 ` Kyle Moffett
2006-02-14 4:28 ` Alan Stern
2006-02-14 5:11 ` Kyle Moffett
2006-02-14 15:33 ` Alan Stern
2006-02-14 6:27 ` Phillip Susi
2006-02-14 16:23 ` Kyle Moffett
2006-02-14 18:39 ` Phillip Susi
2006-02-14 19:55 ` Kyle Moffett
2006-02-14 21:13 ` Phillip Susi
2006-02-14 23:32 ` Kyle Moffett
2006-02-15 3:08 ` Phillip Susi
2006-02-14 19:14 ` Olivier Galibert
2006-02-14 19:37 ` Phillip Susi
2006-02-17 21:04 ` Pavel Machek
2006-02-18 16:34 ` Phillip Susi
2006-02-18 17:29 ` Pavel Machek
2006-02-19 5:52 ` Phillip Susi
2006-02-19 9:02 ` Pavel Machek
2006-02-19 16:35 ` Phillip Susi
2006-02-19 16:41 ` Alan Stern
2006-02-19 19:17 ` Phillip Susi
2006-02-19 19:43 ` Pavel Machek [this message]
2006-02-20 0:56 ` Olivier Galibert
2006-02-20 1:01 ` Pavel Machek
2006-02-20 1:26 ` Olivier Galibert
2006-02-20 4:04 ` Alan Stern
2006-02-19 20:16 ` Bernd Eckenfels
2006-02-18 21:04 ` Alan Stern
2006-02-19 0:02 ` Andrew Morton
2006-02-19 6:02 ` Phillip Susi
2006-02-19 6:32 ` Andrew Morton
2006-02-19 16:39 ` Phillip Susi
2006-02-19 16:54 ` Alan Stern
2006-02-19 20:02 ` Andrew Morton
2006-02-19 20:44 ` Oliver Neukum
2006-02-19 21:02 ` Andrew Morton
2006-02-20 6:55 ` Oliver Neukum
2006-02-20 7:29 ` Andrew Morton
2006-02-20 7:57 ` Andrew Morton
2006-02-14 14:15 ` hackmiester / Hunter Fuller
2006-02-15 23:51 ` Pavel Machek
2006-02-13 2:25 ` Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2006-02-13 19:16 David Brownell
2006-02-13 20:08 ` Phillip Susi
2006-02-14 3:10 ` David Brownell
2006-02-14 6:05 ` Phillip Susi
2006-02-14 17:04 ` David Brownell
2006-02-15 23:43 ` Pavel Machek
2006-02-18 20:51 ` David Brownell
2006-02-19 6:06 ` Phillip Susi
2006-02-20 5:50 ` David Brownell
2006-02-20 16:07 ` Phillip Susi
2006-02-20 16:51 ` Olivier Galibert
2006-02-20 18:20 ` Phillip Susi
2006-02-20 18:44 ` Olivier Galibert
2006-02-20 21:45 ` Phillip Susi
2006-02-21 16:19 ` David Brownell
2006-02-21 18:30 ` Phillip Susi
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=20060219194343.GA15311@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=alon.barlev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=psusi@cfl.rr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox