From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: finding your own dead "CONFIG_" variables Date: Thu, 3 May 2007 12:02:56 +0200 Message-ID: <200705031202.56805.arnd@arndb.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Satyam Sharma , Linux Kernel Mailing List , netdev@vger.kernel.org To: "Robert P. J. Day" Return-path: Received: from moutng.kundenserver.de ([212.227.126.187]:54429 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161458AbXECKDH convert rfc822-to-8bit (ORCPT ); Thu, 3 May 2007 06:03:07 -0400 In-Reply-To: Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thursday 03 May 2007, Robert P. J. Day wrote: > > Suggest: configfiles=3D$(find . -name 'Kconfig*' -or -name '*defcon= fig*') > > > > Some CONFIG_ options exist that are not declared anywhere in the > > Kconfig files but defined directly in the arch/.../*defconfig* > > files. >=20 > it's my understanding that entries in any defconfig files are > *automatically* pruned at some point once a CONFIG_ variable no longe= r > exists in any Kconfig file, so i'm not going to be touching those > files. =A0also, adding that extra check wouldn't add anything useful = to > the output. An interesting category would be a symbol that is - used in a source file - defined in an old defconfig - not present in any Kconfig* file If any of these exist, I would consider them _worse_ than the ones found by your initial script, because some functionality that once was there has been recently removed. Arnd <><