Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933231Ab3D2XqS (ORCPT ); Mon, 29 Apr 2013 19:46:18 -0400 Received: from mail-vb0-f46.google.com ([209.85.212.46]:35665 "EHLO mail-vb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932625Ab3D2XqR (ORCPT ); Mon, 29 Apr 2013 19:46:17 -0400 MIME-Version: 1.0 In-Reply-To: <517EF9AB.8080508@linux.intel.com> References: <1367271946-7239-1-git-send-email-ccross@android.com> <1367271946-7239-8-git-send-email-ccross@android.com> <517EF9AB.8080508@linux.intel.com> Date: Mon, 29 Apr 2013 16:46:15 -0700 X-Google-Sender-Auth: l8AJXgqkC4zdiub_fgS9fxalpzM Message-ID: Subject: Re: [PATCH 07/10] futex: use freezable blocking call From: Colin Cross To: Darren Hart Cc: Linux PM list , lkml , "Rafael J. Wysocki" , =?ISO-8859-1?Q?Arve_Hj=F8nnev=E5g?= , Thomas Gleixner , Andrew Morton , Randy Dunlap , Al Viro , Matthew Helsley Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 786 Lines: 18 On Mon, Apr 29, 2013 at 3:52 PM, Darren Hart wrote: > Colin, > > I don't know anything about when or when not to use freezable*, and I > suspect that may be true for others as well. A more complete > description of why it's acceptable here in the commit log might help > expedite acceptance. > Sure, how about: This call can be converted to a freezable call because it doesn't hold any locks or release any resources when interrupted that might be needed by another freezing task or a kernel driver during suspend. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/