Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1945974AbbEVJwa (ORCPT ); Fri, 22 May 2015 05:52:30 -0400 Received: from lb1-smtp-cloud3.xs4all.net ([194.109.24.22]:36352 "EHLO lb1-smtp-cloud3.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757764AbbEVJw1 (ORCPT ); Fri, 22 May 2015 05:52:27 -0400 Message-ID: <1432288344.27695.86.camel@x220> Subject: Re: regulator: da9062: undefined Kconfig option MFD_DA9062 From: Paul Bolle To: Mark Brown Cc: Valentin Rothberg , stwiss.opensource@diasemi.com, lgirdwood@gmail.com, support.opensource@diasemi.com, linux-kernel@vger.kernel.org, Andreas Ruprecht , hengelein Stefan Date: Fri, 22 May 2015 11:52:24 +0200 In-Reply-To: <20150522093534.GR21577@sirena.org.uk> References: <20150522093534.GR21577@sirena.org.uk> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1348 Lines: 31 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. But we have to mention these things, for reasons like: - the unknown symbol might simply be caused by a typo; - the unknown symbol might change name while drivers depending on it are already merged (we had such a situation last year, didn't we?); - the symbol might not make it into the tree at all (or take _very_ long to get there). 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. Paul Bolle -- 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/