Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756790Ab0GMOlu (ORCPT ); Tue, 13 Jul 2010 10:41:50 -0400 Received: from eu1sys200aog113.obsmtp.com ([207.126.144.135]:49130 "EHLO eu1sys200aog113.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756565Ab0GMOlt convert rfc822-to-8bit (ORCPT ); Tue, 13 Jul 2010 10:41:49 -0400 From: Sundar R IYER To: Mark Brown Cc: "lrg@slimlogic.co.uk" , "sameo@linux.intel.com" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , STEricsson_nomadik_linux , Linus WALLEIJ , Bengt JONSSON Date: Tue, 13 Jul 2010 16:41:34 +0200 Subject: RE: [PATCH v2 2/2] ux500: add ab8500-regulators machine specific data Thread-Topic: [PATCH v2 2/2] ux500: add ab8500-regulators machine specific data Thread-Index: AcsilkagbtvBPamhS+iDfD/P7dyh5gAAlHWw Message-ID: <33A307AF30D7BF4F811B1568FE7A9B1810E7E88D@EXDCVYMBSTM006.EQ1STM.local> References: <1279030173-3086-1-git-send-email-sundar.iyer@stericsson.com> <1279030173-3086-2-git-send-email-sundar.iyer@stericsson.com> <20100713141828.GB24260@rakim.wolfsonmicro.main> In-Reply-To: <20100713141828.GB24260@rakim.wolfsonmicro.main> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1469 Lines: 32 Mark, >It is extremely disappointing to see you reposting this without engaging >with my previous review at all. Sincere apologies. As I said, I tried to repost after fixing your comments; but my mistake that I didn't engage prior to the posting. >> +static struct regulator_consumer_supply ab8500_vaux1_consumers[] = { >> + { .dev = NULL, .supply = "vaux1", }, >> +}; > >All these supplies with NULL devices are bogus, supplies are in terms of >the device being supplied not the labels on the board. If you've got a >supply with no device and the name of the supply on either the regulator >or the board you're most likely doing it wrong. The only exception is >for supplies used in cpufreq since we don't have a struct device we can >use there. I had these supplies as NULL, so that later on, when we add devices for our platform, each developer can edit this file to hook up his own device. The reason I wanted this file in the patch set was to include the machine constraints for the regulators on AB8500. As admitted earlier, I will wait for your valuable comments before posting the next patch set. (Also, I will try to make sure(still learning) to post the next patches into the same thread.) Regards, Sundar -- 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/