From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755500Ab0ETKU2 (ORCPT ); Thu, 20 May 2010 06:20:28 -0400 Received: from smtp.nokia.com ([192.100.105.134]:41353 "EHLO mgw-mx09.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751826Ab0ETKU0 (ORCPT ); Thu, 20 May 2010 06:20:26 -0400 Date: Thu, 20 May 2010 13:15:34 +0300 From: Felipe Balbi To: ext Florian Mickler Cc: "me@felipebalbi.com" , "Balbi Felipe (Nokia-D/Helsinki)" , ext James Bottomley , Kevin Hilman , Alan Stern , "linux-omap@vger.kernel.org" , "Theodore Ts'o" , Geoff Smith , Brian Swetland , Kernel development list , Oleg Nesterov , Mark Brown , Tejun Heo , Linux-pm mailing list , Arjan van de Ven , Liam Girdwood , Matthew Garrett , Andrew Morton , Linus Torvalds Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6) Message-ID: <20100520101534.GH9992@nokia.com> Reply-To: felipe.balbi@nokia.com References: <1274124267.4418.149.camel@mulgrave.site> <20100517193840.GB14047@gandalf> <20100517193952.GC14047@gandalf> <1274125775.4418.182.camel@mulgrave.site> <20100518064022.GA6522@nokia.com> <1274191188.10304.5.camel@mulgrave.site> <20100519065934.GH12879@nokia.com> <20100520071528.494c38e4@schatten.dmk.lab> <20100520085739.GB14584@gandalf> <20100520120519.0d27d6bf@schatten.dmk.lab> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20100520120519.0d27d6bf@schatten.dmk.lab> User-Agent: Mutt/1.5.20 (2009-06-14) X-OriginalArrivalTime: 20 May 2010 10:17:55.0256 (UTC) FILETIME=[B66C5B80:01CAF805] X-Nokia-AV: Clean Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Thu, May 20, 2010 at 12:05:19PM +0200, ext Florian Mickler wrote: >You said that already. For me this sounds like you want to take the >users hostage in order to get nice (poweraware) apps. not the users, no. The app developers. They should know what bad applications can cause to a nicely done system. >Robust system design can take crap and perform well. Users will most of >the time prefer a robust system over a nicely designed system. (Just >think of the ak-47) (hope you're talking about the gun :-p) put some bad bullets on ak-47 and see if it behaves well, a really crappy trigger will also make it fail. How robust can a system be with badly chosen components ? >I think we just have to agree to disagree here? I think so. -- balbi DefectiveByDesign.org