Re: identifying CONFIG variable typoes in the source tree

2007-01-24 Thread Robert P. J. Day
On Wed, 24 Jan 2007, Geert Uytterhoeven wrote: > On Tue, 23 Jan 2007, Robert P. J. Day wrote: > > let's check these: > > > > $ grep -r 53C700_BE_BUS . > > ./drivers/scsi/53c700.h:#ifdef CONFIG_53C700_BE_BUS > > This is the core support for big endian 53c700 SCSI busses. It's > needed for various

Re: identifying CONFIG variable typoes in the source tree

2007-01-24 Thread Geert Uytterhoeven
On Tue, 23 Jan 2007, Robert P. J. Day wrote: > let's check these: > > $ grep -r 53C700_BE_BUS . > ./drivers/scsi/53c700.h:#ifdef CONFIG_53C700_BE_BUS This is the core support for big endian 53c700 SCSI busses. It's needed for various m68k machines, patch to be submitted when the m68k support is

Re: identifying CONFIG variable typoes in the source tree

2007-01-23 Thread Robert P. J. Day
On Tue, 23 Jan 2007, Oleg Verych wrote: > On 2007-01-23, Robert P. J. Day wrote: > [] > > what it does is scan the entire tree for lines of the form > > > > ...if... CONFIG_whatever... > > > > collects all of those CONFIG variables and, one at a time, checks to > > see if that variable even exi

Re: identifying CONFIG variable typoes in the source tree

2007-01-23 Thread Oleg Verych
On 2007-01-23, Robert P. J. Day wrote: [] > what it does is scan the entire tree for lines of the form > > ...if... CONFIG_whatever... > > collects all of those CONFIG variables and, one at a time, checks to > see if that variable even exists in any Kconfig file in the tree so > that it could pos

identifying CONFIG variable typoes in the source tree

2007-01-23 Thread Robert P. J. Day
because it's cold outside and i was bored, i put together the following script, to be run from the top of the source tree: ==B #!/bin/sh CV=$(grep -rh "^#.*if.* CONFIG_[A-Za-z0-9]" . | grep -v endif) CVARS=$(echo "${CV}" | sed "s/.*\(CONFIG_[