linux-kernel - Re: [PATCH] tags: fix config symbols generation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090206150858.GA15565@padd.com>
Date:	Fri, 6 Feb 2009 07:08:58 -0800
From:	Pete Wyckoff <pw@...d.com>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	sam@...nborg.org, akpm@...l.org, albcamus@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tags: fix config symbols generation

adobriyan@...il.com wrote on Thu, 29 Jan 2009 13:26 +0300:
> commit 4f628248a578585472e19e4cba2c604643af8c6c aka
> "kbuild: reintroduce ALLSOURCE_ARCHS support for tags/cscope"
> breaks tags generation for Kconfig symbols.
> 
> Steps to reproduce:
> 
> 	make tags
> 	vi -t PROC_FS
> 
> It should jump to 'config PROC_FS' line.
> 
> Signed-off-by: Alexey Dobriyan <adobriyan@...il.com>
> ---
> 
>  scripts/tags.sh |    5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> --- a/scripts/tags.sh
> +++ b/scripts/tags.sh
> @@ -76,7 +76,10 @@ all_sources()
>  
>  all_kconfigs()
>  {
> -	find_sources $ALLSOURCE_ARCHS 'Kconfig*'
> +	for arch in $ALLSOURCE_ARCHS; do
> +		find_sources $arch 'Kconfig*'
> +	done
> +	find_other_sources 'Kconfig*'
>  }
>  
>  all_defconfigs()

Yes, this is necessary.  It fixes the problem introduced by
4f628248a578585472e19e4cba2c604643af8c6c (kbuild: reintroduce
ALLSOURCE_ARCHS support for tags/cscope).

Tested-by: Pete Wyckoff <pw@...d.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/