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
| ||
|
Date: Thu, 13 May 2010 10:33:10 -0700 From: Daniel Walker <dwalker@...o99.com> To: Matthew Garrett <mjg@...hat.com> Cc: Paul Walmsley <paul@...an.com>, Arve Hjønnevåg <arve@...roid.com>, linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>, Oleg Nesterov <oleg@...hat.com>, Tony Lindgren <tony@...mide.com>, Kevin Hilman <khilman@...prootsystems.com>, Alan Stern <stern@...land.harvard.edu>, magnus.damm@...il.com, Theodore Ts'o <tytso@....edu>, mark gross <mgross@...ux.intel.com>, Arjan van de Ven <arjan@...radead.org>, Geoff Smith <geoffx.smith@...el.com>, Brian Swetland <swetland@...gle.com>, "Rafael J. Wysocki" <rjw@...k.pl>, Benoît Cousson <b-cousson@...com>, linux-omap@...r.kernel.org, Vitaly Wool <vitalywool@...il.com>, Linus Walleij <linus.walleij@...csson.com>, Mark Brown <broonie@...nsource.wolfsonmicro.com>, Liam Girdwood <lrg@...mlogic.co.uk> Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6) On Thu, 2010-05-13 at 13:17 +0100, Matthew Garrett wrote: > On Wed, May 12, 2010 at 09:35:30PM -0600, Paul Walmsley wrote: > > > > Figuring out a different way to do this should not limit Android at all, > > since Google can do what other Linux distributions do and continue to > > patch opportunistic suspend/suspend-block calls into their kernels as > > needed to ship devices, while contributing towards a different solution to > > the problem. > > I basically agree, except that despite having a year to do so none of us > have come up with a different way that would actually work. Google have > done this work. Who's going to prove that there is actually a different > way to do this? We all feel the pain of inelegance right? I think it's clear that this system will not last (but there's no other immediate option) .. That doesn't mean we should reject it, but we need to be clear that this system will get replaced. So we should format the patches appropriately. To me the userspace aspect is a permanent change .. If we could drop that (or put it into debugfs) then it would make this a lot easy to accept as a stepping stone. Daniel -- 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