Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756802AbbEVI6J (ORCPT ); Fri, 22 May 2015 04:58:09 -0400 Received: from mail1.bemta3.messagelabs.com ([195.245.230.173]:10737 "EHLO mail1.bemta3.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752120AbbEVI6D (ORCPT ); Fri, 22 May 2015 04:58:03 -0400 X-Env-Sender: stwiss.opensource@diasemi.com X-Msg-Ref: server-14.tower-39.messagelabs.com!1432285068!13702483!1 X-Originating-IP: [94.185.165.51] X-StarScan-Received: X-StarScan-Version: 6.13.15; banners=-,-,- X-VirusChecked: Checked From: "Opensource [Steve Twiss]" To: Valentin Rothberg , "Lee Jones (lee.jones@linaro.org)" , "broonie@kernel.org" CC: "lgirdwood@gmail.com" , Support Opensource , "linux-kernel@vger.kernel.org" , Paul Bolle , "Andreas Ruprecht" , hengelein Stefan Subject: RE: regulator: da9062: undefined Kconfig option MFD_DA9062 Thread-Topic: regulator: da9062: undefined Kconfig option MFD_DA9062 Thread-Index: AQHQlGg0zYoloTGpzUKnmNwjnapyxZ2HrGHQ Date: Fri, 22 May 2015 08:57:47 +0000 Message-ID: <6ED8E3B22081A4459DAC7699F3695FB7014B22C9D5@SW-EX-MBX02.diasemi.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.20.26.77] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id t4M8wB71025294 Content-Length: 2150 Lines: 55 On 22 May 2015 09:20 Valentin Rothberg wrote: > To: Opensource [Steve Twiss] > Cc: broonie@kernel.org; lgirdwood@gmail.com; Support Opensource; linux- > kernel@vger.kernel.org; Paul Bolle; Andreas Ruprecht; hengelein Stefan > Subject: regulator: da9062: undefined Kconfig option MFD_DA9062 > > Hi Steve, > > your commit 4068e5182ada ("regulator: da9062: DA9062 regulator > driver") is in today's linux-next tree (i.e., next-20150522) and adds > the following lines of code to drivers/regulator/Kconfig: > > +config REGULATOR_DA9062 > + tristate "Dialog Semiconductor DA9062 regulators" > + depends on MFD_DA9062 > > MFD_DA9062 is not defined in Kconfig, so that the dependency is always > false. Hence, the da9062-regulator driver cannot be compiled at the > current state. > > Is there a patch queued somewhere to add the missing Kconfig option? Hi Valentin, Mark applied the DA9062 regulator patch into linux-next yesterday, but looking at my e-mail history the MFD components are still waiting to be applied I think. The MFD component has been reviewed in earlier threads ... [PATCH V1 1/6] mfd: da9062: DA9062 MFD core driver -- https://lkml.org/lkml/2015/4/17/519 [PATCH V2 1/4] mfd: da9062: DA9062 MFD core driver -- https://lkml.org/lkml/2015/5/14/531 [PATCH V3 1/4] mfd: da9062: DA9062 MFD core driver -- https://lkml.org/lkml/2015/5/19/523 And the last patch V3 for the MFD seems to have been a little quiet. But, also there were three other patches with this set, mfd: da9062: DA9062 MFD core driver watchdog: da9062: DA9062 watchdog driver devicetree: da9062: Add bindings for DA9062 driver Hi Lee/Mark, I'm not sure if the MFD part was missed or if I have not followed the rules properly on my submissions for DA9062 MFD & regulators. Could I ask if you would take a quick look please? Regards, Steve > I detected this issue with scripts/checkkconfigsymbols.py by diffing > yesterday's and today's linux-next tree. > > Kind regards, > Valentin ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?