linux-kernel - Re: Kconfig style question

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 16 Mar 2007 21:09:27 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Bodo Eggert <7eggert@....de>
Cc:	Kumar Gala <galak@...nel.crashing.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Roman Zippel <zippel@...ux-m68k.org>
Subject: Re: Kconfig style question

On Fri, Mar 16, 2007 at 08:53:53AM +0100, Bodo Eggert wrote:
> Kumar Gala <galak@...nel.crashing.org> wrote:
> 
> > For source lines I've seen both:
> > 
> > source "arch/powerpc/platforms/52xx/Kconfig"
> > 
> > and
> > 
> > source arch/powerpc/platforms/85xx/Kconfig
> > 
> > Is there a preferred style?  Quotes or not?
> 
> $ find . -name Kconfig -exec grep ^source '{}' \;|grep \"|wc -l
>     732
> $ find . -name Kconfig -exec grep ^source '{}' \;|grep -v \"|wc -l
>      44

Which is somewaht funny.
source is defined like this:
"source" <prompt>

Where <prompt> may be a single string without spaces or
a quoted string with spaces.
So kconfig allow you to use spaces in the path/filename. But
then most users uses "" despite it is not needed since we obviously
do not use spaces in path/filename in the kernel due to
make limitations (and good taste).

	Sam
-
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/