linux-kernel - Re: [RFC v2 1/4] backports: replace CPTCFG prefix for CONFIG

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1415046029.2726.6.camel@sipsolutions.net>
Date:	Mon, 03 Nov 2014 21:20:29 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	"Luis R. Rodriguez" <mcgrof@...e.com>
Cc:	"backports@...r.kernel.org" <backports@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Yann E. MORIN" <yann.morin.1998@...e.fr>,
	Michal Marek <mmarek@...e.cz>,
	Stefan Assmann <sassmann@...nic.de>
Subject: Re: [RFC v2 1/4] backports: replace CPTCFG prefix for
 CONFIG_BACKPORT

On Mon, 2014-11-03 at 11:56 -0800, Luis R. Rodriguez wrote:

> With my current code I end up with on a package (not integration):
> 
> config BACKPORT_BUILD_AVERAGE
>         bool
>         depends on !AVERAGE
>         default y if BACKPORT_USERSEL_BUILD_ALL
>         default y if BACKPORT_AVERAGE
>         #h-file linux/average.h
>         #c-file lib/average.c
> 
> config BACKPORT_AVERAGE
>         bool
> 
> 
> I do see I on the package with this on the Makfile though:
> 
> 
> compat-$(CONFIG_BACKPORT_BACKPORT_BUILD_AVERAGE) += lib-average.o
> 
> Would it not suffice to just ensure we don't have BACKPORT_BACKPORT_
> here and just BACKPORT_ once ?

The BACKPORT_BACKPORT_ is actually correct ... but it'll be really hard
to make sense of :-)

johannes

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