Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755972Ab1CCLty (ORCPT ); Thu, 3 Mar 2011 06:49:54 -0500 Received: from metis.ext.pengutronix.de ([92.198.50.35]:33898 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750909Ab1CCLtx (ORCPT ); Thu, 3 Mar 2011 06:49:53 -0500 Date: Thu, 3 Mar 2011 12:49:49 +0100 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= To: Thomas Gleixner Cc: linux@arm.linux.org.uk, Dinh.Nguyen@freescale.com, s.hauer@pengutronix.de, linux-kernel@vger.kernel.org, xiao-lizhang@freescale.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCHv1] ARM: imx: Add support for low power suspend on MX51. Message-ID: <20110303114949.GQ22310@pengutronix.de> References: <1299086278-12131-1-git-send-email-Dinh.Nguyen@freescale.com> <20110302215238.GK22310@pengutronix.de> <20110303093532.GO22310@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: 2001:6f8:1178:2:215:17ff:fe12:23b0 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1660 Lines: 41 Hello Thomas, On Thu, Mar 03, 2011 at 12:02:15PM +0100, Thomas Gleixner wrote: > On Thu, 3 Mar 2011, Uwe Kleine-K?nig wrote: > > On Thu, Mar 03, 2011 at 12:51:32AM +0100, Thomas Gleixner wrote: > > > > > +static int __init mx5_pm_init(void) > > > > I'd prefer to have that called by imx51_init_early. > > > > > > And the reason is? > > > > > > 1) your personal preference > > > 2) there is some useful technical reason > > > > > > If #1, then this comment was just waste of electrons > > > If #2, you failed to provide some reasonable explanation > > Actually it's #2, and to quote a different review[1]: > > > > Reviewers hint to a correct solution and you are supposed to > > lookup what that solution means and act accordingly. If you do > > not understand the hint or its implications please ask [...] > > I said the above when I hinted to use DEFINE_SPINLOCK(lock) instead of > static spinlock_t lock. And that requires to lookup what > DEFINE_SPINLOCK() actually does, which is a reasonable request. > > How is the author of that code supposed to figure out what the merit > of s/mx5_pm_init/imx51_init_early/ is? By looking up your preferences > in google or what? Note I didn't suggest to change the function name. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ | -- 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/