From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vitaly Wool Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8) Date: Wed, 26 May 2010 13:23:14 +0200 Message-ID: References: <1274482015-30899-1-git-send-email-arve@android.com> <1274863655.5882.4875.camel@twins> <1274867106.5882.5090.camel@twins> <1274868593.5882.5185.camel@twins> <1274869966.5882.5262.camel@twins> <1274870970.5882.5311.camel@twins> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: =?ISO-8859-1?Q?Arve_Hj=F8nnev=E5g?= Cc: Peter Zijlstra , LKML , felipe.balbi@nokia.com, Linux OMAP Mailing List , Linux PM List-Id: linux-omap@vger.kernel.org 2010/5/26 Arve Hj=F8nnev=E5g : > Fixing the actually issue means fixing all user-space code, and > replacing most x86 hardware. I don't think keeping this feature out o= f > the kernel will significantly accelerate this. But if this feature gets merged, I bet you'll find another 100 reasons to not fix the actual issue. I wouldn't say so if you haven't provided the irrelevant points already, like "replacing x86 hardware". You're trying to merge the approach which makes the bad way of handing things the easiest way. This shouldn't get in as it is IMO. ~Vitaly