On Thu, 13 Sep 2007, Adrian Bunk wrote:If done right (and autosuspend now is), there is no "required" userspace. If you want autosuspend, you just say so. The kernel doesn't do it by default. This is not about "user space required" - it's about "user space can ask for it if it wants to". Notice? There doesn't even have to be any blacklists/whitelists at all. It really can be just an application that allows the user to check or uncheck the capability (with a warning saying something like: "Some USB devices may disconnect when suspended - if this affects you, uncheck this"). That's why the kernel shouldn't set policy. It's a *good* thing to just expose the capabilities, but not necessarily use them! Linus -
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Stephen Rothwell | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 33/37] dccp: Initialisation framework for feature negotiation |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
