| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <alpine.LFD.2.00.0912071337020.3560@localhost.localdomain> Date: Mon, 7 Dec 2009 13:41:50 -0800 (PST) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Alan Stern <stern@...land.harvard.edu> cc: Zhang Rui <rui.zhang@...el.com>, "Rafael J. Wysocki" <rjw@...k.pl>, LKML <linux-kernel@...r.kernel.org>, ACPI Devel Maling List <linux-acpi@...r.kernel.org>, pm list <linux-pm@...ts.linux-foundation.org> Subject: Re: [GIT PULL] PM updates for 2.6.33 On Mon, 7 Dec 2009, Alan Stern wrote: > > It only seems that way because you didn't take into account devices > that suspend synchronously but whose children suspend asynchronously. But why would I care? If somebody suspends synchronously, then that's what he wants. > A synchronous suspend routine for a device with async child suspends > would have to look just like your usb_node_suspend(): Sure. But that sounds like a "Doctor, it hurts when I do this" situation. Don't do that. Make the USB host controller do its suspend asynchronously. We don't suspend PCI bridges anyway, iirc (but I didn't actually check). And at worst, we can make the PCI _bridges_ know about async suspends, and solve it that way - without actually making any normal PCI drivers do it. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists