Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754378Ab1CKUfa (ORCPT ); Fri, 11 Mar 2011 15:35:30 -0500 Received: from cantor2.suse.de ([195.135.220.15]:57998 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753833Ab1CKUf1 (ORCPT ); Fri, 11 Mar 2011 15:35:27 -0500 Date: Fri, 11 Mar 2011 12:33:05 -0800 From: Greg KH To: "Rafael J. Wysocki" Cc: LKML , Len Brown , Kay Sievers , Jesse Barnes , Linux PM mailing list , "H. Peter Anvin" , mingo@redhat.com, tglx@linutronix.de Subject: Re: [RFC][PATCH 2/2] Convert several sysdev users to using struct syscore_ops Message-ID: <20110311203305.GA21045@suse.de> References: <201103100131.58206.rjw@sisk.pl> <201103100134.02675.rjw@sisk.pl> <20110311171231.GB10437@suse.de> <201103112129.24876.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201103112129.24876.rjw@sisk.pl> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1672 Lines: 36 On Fri, Mar 11, 2011 at 09:29:24PM +0100, Rafael J. Wysocki wrote: > I thought about two different possible ways forward: > > (1) Push [1/2] and the patches converting things that x86 depends on first, > followed perhaps by a patch introducing something like > CONFIG_ARCH_NO_SYSDEV_OPS that would simply disable > sysdev_{suspend|resume|shutdown}() (x86 would set it). The other arches > might then be converted over time. > > (2) Prepare patches converting everything that can be converted in the tree > and push them all in one shot. > > The advantage of (1) is that we can start making changes RSN and the > advantage of (2) seems to be that we may avoid some potential suspend/resume > ordering issues on non-x86 architectures that may arise in principle if some > subsystems are converted to using struct syscore_ops while the others are > not (syscore_suspend() is executed after sysdev_suspend(), so if we move > something from the latter to the former, it may end up being executed after > things that it was executed before previously). > > Please let me know what your opinion is. Hm, I would prefer (1) as that lets us get this moving sooner, and "flag days" are never good to have. If there are problems that arise because of it, as you have noted, it will be simple just to convert the parts that were using the "old" methods to the new ones to fix the issue, right? thanks, greg k-h -- 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/