Re: regulator: da9062: undefined Kconfig option MFD_DA9062

[Mark Brown <broonie@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]

On Fri, May 22, 2015 at 11:52:24AM +0200, Paul Bolle wrote:
> On Fri, 2015-05-22 at 10:35 +0100, Mark Brown wrote:

> > > Is there a patch queued somewhere to add the missing Kconfig option?

> > This is totally normal for merging MFDs where the MFD goes in via the
> > MFD tree and the subsystem drivers go in via their trees.  This way
> > subsystem maintainers don't have to sit through endless resends of the
> > core driver.

> So every time a driver is added to linux-next that depends on an unknown
> symbol a boring message like this will be sent. And people can simply
> respond to it with a link to the patch that adds the missing symbol. 

> It's a bit annoying. But it helps in catching errors as early as
> possible. And it gives the people looking into these kconfig oddities
> the info they need to keep track of things.

For the common cases like new things being added over multiple trees I
would expect people to be making some effort to filter these things
before reporting manually - for example here a couple of moments of
searching would have shown the rest of the series under review, or most
likely waiting a few weeks before reporting would allow the MFD to get
merged.

One effect of being too keen to report things is that a high false
positive rate will cause people to pay less attention, if the source is
usually just generating noise then it gets tuned out.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]