From: Lee Jones <lee.jones@linaro.org>
To: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Support Opensource <Support.Opensource@diasemi.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Paul Bolle <pebolle@tiscali.nl>,
Andreas Ruprecht <andreas.ruprecht@fau.de>,
hengelein Stefan <stefan.hengelein@fau.de>
Subject: Re: regulator: da9062: undefined Kconfig option MFD_DA9062
Date: Tue, 26 May 2015 11:37:13 +0100 [thread overview]
Message-ID: <20150526103713.GG11677@x1> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB7014B22C9D5@SW-EX-MBX02.diasemi.com>
On Fri, 22 May 2015, Opensource [Steve Twiss] wrote:
> 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?
Nothing has been missed. I have been very busy, but I will get round
to reviewing. Your patch is marked as 'important' and is stilling in
my inbox. My plan is to clear my back-log today.
> > I detected this issue with scripts/checkkconfigsymbols.py by diffing
> > yesterday's and today's linux-next tree.
> >
> > Kind regards,
> > Valentin
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-05-26 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 8:20 regulator: da9062: undefined Kconfig option MFD_DA9062 Valentin Rothberg
2015-05-22 8:57 ` Opensource [Steve Twiss]
2015-05-26 10:37 ` Lee Jones [this message]
2015-05-27 7:19 ` Opensource [Steve Twiss]
2015-05-22 9:35 ` Mark Brown
2015-05-22 9:52 ` Paul Bolle
2015-05-22 10:12 ` Mark Brown
2015-05-22 10:53 ` Valentin Rothberg
2015-05-22 13:07 ` Mark Brown
2015-05-22 14:03 ` Paul Bolle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150526103713.GG11677@x1 \
--to=lee.jones@linaro.org \
--cc=Support.Opensource@diasemi.com \
--cc=andreas.ruprecht@fau.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=stefan.hengelein@fau.de \
--cc=stwiss.opensource@diasemi.com \
--cc=valentinrothberg@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox