lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 22 May 2015 08:57:47 +0000
From:	"Opensource [Steve Twiss]" <stwiss.opensource@...semi.com>
To:	Valentin Rothberg <valentinrothberg@...il.com>,
	"Lee Jones (lee.jones@...aro.org)" <lee.jones@...aro.org>,
	"broonie@...nel.org" <broonie@...nel.org>
CC:	"lgirdwood@...il.com" <lgirdwood@...il.com>,
	Support Opensource <Support.Opensource@...semi.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Paul Bolle <pebolle@...cali.nl>,
	"Andreas Ruprecht" <andreas.ruprecht@....de>,
	hengelein Stefan <stefan.hengelein@....de>
Subject: RE: regulator: da9062: undefined Kconfig option MFD_DA9062

On 22 May 2015 09:20 Valentin Rothberg wrote:

> To: Opensource [Steve Twiss]
> Cc: broonie@...nel.org; lgirdwood@...il.com; Support Opensource; linux-
> kernel@...r.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ