Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934444AbbGVOnA (ORCPT ); Wed, 22 Jul 2015 10:43:00 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:33424 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S932206AbbGVOm6 (ORCPT ); Wed, 22 Jul 2015 10:42:58 -0400 X-Listener-Flag: 11101 Message-ID: <1437576174.30329.84.camel@mtksdaap41> Subject: Re: [PATCH v2 2/2] regulator: mt6311: Add support for mt6311 regulator From: Henry Chen To: Javier Martinez Canillas CC: Mark Brown , Mark Rutland , Liam Girdwood , Linux Kernel , , "Sascha Hauer" , Matthias Brugger , , "linux-arm-kernel@lists.infradead.org" Date: Wed, 22 Jul 2015 22:42:54 +0800 In-Reply-To: References: <1437566453-13117-1-git-send-email-henryc.chen@mediatek.com> <1437566453-13117-3-git-send-email-henryc.chen@mediatek.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 994 Lines: 32 On Wed, 2015-07-22 at 14:50 +0200, Javier Martinez Canillas wrote: > > + > > +struct mt6311 { > > + struct device *dev; > > + struct regmap *regmap; > > + struct regulator_dev *rdev[MT6311_MAX_REGULATORS]; > > + int num_regulator; > > + int chip_cid; > > +}; > > It seems this struct can be removed, the rdev, num_regulator and > chip_cid fields are set but not used and dev and regmap are only used > to set the struct regulator_config fields in mt6311_regulator_init(). > But that won't be necessary if you just remove the > mt6311_regulator_init() function and move the regulator registration > logic to mt6311_i2c_probe(). Yes, it should be removed, thanks for the advise. Henry > > Best regards, > Javier -- 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/