On Thu, Jan 31, 2019 at 4:28 AM Mark Brown [off-list ref] wrote:

On Thu, Jan 31, 2019 at 09:15:01AM +0100, Bartosz Golaszewski wrote:

quoted

I'm not sure what the policy is on merging MFD drivers, but I'm seeing
that Mark Brown has already picked up the regulator part into his tree
(including the binding document). I think you can just pick up the
input patches and it will simply not show up in Kconfig until the core
mfd module is upstream.

quoted

@Mark: could you please confirm it?

Right, as it's a new MFD the Kconfig will stop it causing build breakage
until the MFD is merged.  I'm doing it partly just to cut down on the
amount of mail from resends while the rest of the series gets reviewed.

Ugh, I might have pulled it in if it did not reference the new header
file. As a rule I try to enable all symbols that result in input
devices being created so as much of input code is covered... I'd
prefer input piece be merged with MFD.

Thanks.

-- 
Dmitry