From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6) Date: Thu, 13 May 2010 13:17:45 +0100 Message-ID: <20100513121745.GA10749@srcf.ucam.org> References: <1272667021-21312-1-git-send-email-arve@android.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Paul Walmsley Cc: Arve =?iso-8859-1?B?SGr4bm5lduVn?= , linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Tejun Heo , Oleg Nesterov , Tony Lindgren , Kevin Hilman , Alan Stern , magnus.damm@gmail.com, Theodore Ts'o , mark gross , Arjan van de Ven , Geoff Smith , Brian Swetland , "Rafael J. Wysocki" , =?iso-8859-1?Q?Beno=EEt?= Cousson , linux-omap@vger.kernel.org, Vitaly Wool , Linus Walleij , Mark Brown , Liam Girdwood List-Id: linux-omap@vger.kernel.org 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? -- Matthew Garrett | mjg59@srcf.ucam.org