Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757817AbbEVKMd (ORCPT ); Fri, 22 May 2015 06:12:33 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:51403 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757798AbbEVKM1 (ORCPT ); Fri, 22 May 2015 06:12:27 -0400 Date: Fri, 22 May 2015 11:12:19 +0100 From: Mark Brown To: Paul Bolle Cc: Valentin Rothberg , stwiss.opensource@diasemi.com, lgirdwood@gmail.com, support.opensource@diasemi.com, linux-kernel@vger.kernel.org, Andreas Ruprecht , hengelein Stefan Message-ID: <20150522101219.GT21577@sirena.org.uk> References: <20150522093534.GR21577@sirena.org.uk> <1432288344.27695.86.camel@x220> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KLR62ZwG+3BuLtMl" Content-Disposition: inline In-Reply-To: <1432288344.27695.86.camel@x220> X-Cookie: Positively no smoking. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: regulator: da9062: undefined Kconfig option MFD_DA9062 X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2389 Lines: 57 --KLR62ZwG+3BuLtMl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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.=20 > 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. --KLR62ZwG+3BuLtMl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVXwD9AAoJECTWi3JdVIfQAbMH/1Bf9Af3rPjJHMpWWT93Aito IcdRJQZHMQQe7KsgfVFlz3ScOEtt4rhcT/IAPJHItTED9kS2pYryPCjxs9gHY3it q6YtQk7qG3MbFUI2HQk8xuVPiBw3cYoSUUAr/yPW9Ga2MJeJheqTtjGp9amHGjTU x3YoXYb0GDRiIkDICcEnYY/jmMFPOCoygQQRmntHVxQtiSiKe6IeEP1iCPG9IWXL ZCLH9J+V/o4ysw/UsbolYc/+BEAt5wcZiOsbBKjl411YXo8c0B68And/8hqt+7pG xOKL0lncgjZE+hb45U4XijoxJy3KOix6qAW1ag55FoqXfYCmGacDvkZsVAIch14= =uIbv -----END PGP SIGNATURE----- --KLR62ZwG+3BuLtMl-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/