Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761533AbXEKCdN (ORCPT ); Thu, 10 May 2007 22:33:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754804AbXEKCc6 (ORCPT ); Thu, 10 May 2007 22:32:58 -0400 Received: from az33egw02.freescale.net ([192.88.158.103]:47443 "EHLO az33egw02.freescale.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757489AbXEKCc5 (ORCPT ); Thu, 10 May 2007 22:32:57 -0400 Message-ID: <4643D5B8.8050106@freescale.com> Date: Thu, 10 May 2007 21:32:24 -0500 From: Timur Tabi User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: Simon Horman CC: Kumar Gala , sam@ravnborg.org, Kim Phillips , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, =?ISO-8859-1?Q?Ismail_D=F6nmez?= , Michael Schmitz , Roman Zippel , Geert Uytterhoeven , Johannes Berg , Benjamin Herrenschmidt , Paul Mackerras Subject: Re: Kconfig warnings on latest GIT References: <200705080004.14570.ismail@pardus.org.tr> <20070508143127.38fafa3c.kim.phillips@freescale.com> <4640D988.1040504@freescale.com> <20070510051042.GA16812@verge.net.au> <46434ED0.6030808@freescale.com> <20070511012529.GC10715@verge.net.au> <20070511020545.GG10715@verge.net.au> <20070511022721.GI10715@verge.net.au> In-Reply-To: <20070511022721.GI10715@verge.net.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 511 Lines: 13 Simon Horman wrote: > I agree. I had thought a little about a kconfig fix. Though I'm > wondering if removing the warning will lead to oodles of dangling > symbols and invalid checks over time. I'm pretty sure it will. Perhaps we need to have a lint for Kconfig? - 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/