From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263971AbUKZVmc (ORCPT ); Fri, 26 Nov 2004 16:42:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263960AbUKZVma (ORCPT ); Fri, 26 Nov 2004 16:42:30 -0500 Received: from pop5-1.us4.outblaze.com ([205.158.62.125]:2227 "HELO pop5-1.us4.outblaze.com") by vger.kernel.org with SMTP id S263948AbUKZVj5 (ORCPT ); Fri, 26 Nov 2004 16:39:57 -0500 Subject: Re: Suspend 2 merge: 21/51: Refrigerator upgrade. From: Nigel Cunningham Reply-To: ncunningham@linuxmail.org To: Pavel Machek Cc: Andrew Morton , Linux Kernel Mailing List In-Reply-To: <20041125232519.GI2711@elf.ucw.cz> References: <1101292194.5805.180.camel@desktop.cunninghams> <1101296026.5805.275.camel@desktop.cunninghams> <20041125183332.GJ1417@openzaurus.ucw.cz> <1101420616.27250.65.camel@desktop.cunninghams> <20041125223610.GC2711@elf.ucw.cz> <1101422986.27250.106.camel@desktop.cunninghams> <20041125232519.GI2711@elf.ucw.cz> Content-Type: text/plain Message-Id: <1101426572.27250.151.camel@desktop.cunninghams> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6-1mdk Date: Fri, 26 Nov 2004 10:49:32 +1100 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi. On Fri, 2004-11-26 at 10:25, Pavel Machek wrote: > Hi! > > > > > > > Included in this patch is a new try_to_freeze() macro Andrew M suggested > > > > > > a while back. The refrigerator declarations are put in sched.h to save > > > > > > extra includes of suspend.h. > > > > > > > > > > try_to_freeze looks nice. Could we get it in after 2.6.10 opens? > > > > > > > > I'm hoping to get the whole thing in mm once all these replies are dealt > > > > with. Does that sound unrealistic? > > > > > > Yes, a little ;-). > > > > I'm not talking about talking about problems and then doing nothing :> > > I'm writing a list of changes as I look at each of these responses. > > Assuming they're all addressed (or not changed for good reasons), and > > the code is actually useful, why shouldn't it go into mm? > > It has chance to go into mm, but I do not think all 51 patches will go > at once. And I expect few more rounds of patches / comments. (And then > some patch / "it is too big" flamewar, too :-). Didn't see any flamewar over the size of Reiser4. :> > > > Silently doing nothing when user asked for sync is not nice, > > > either. BUG() is better solution than that. > > > > I don't think we should BUG because the user presses Sys-Rq S while > > suspending. I'll make it BUG_ON() and make the Sys_Rq printk & ignore > > when suspending. Sound reasonable? > > Yes, that's better. ... only that it means just another hook somewhere > :-(. :<. But we're only talking two or three lines. Let's keep it in perspective. -- Nigel Cunningham Pastoral Worker Christian Reformed Church of Tuggeranong PO Box 1004, Tuggeranong, ACT 2901 You see, at just the right time, when we were still powerless, Christ died for the ungodly. -- Romans 5:6