| 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
| ||
|
Message-ID: <1415095985.2064.12.camel@sipsolutions.net> Date: Tue, 04 Nov 2014 11:13:05 +0100 From: Johannes Berg <johannes@...solutions.net> To: "Luis R. Rodriguez" <mcgrof@...not-panic.com> Cc: backports@...r.kernel.org, linux-kernel@...r.kernel.org, yann.morin.1998@...e.fr, mmarek@...e.cz, sassmann@...nic.de, "Luis R. Rodriguez" <mcgrof@...e.com> Subject: Re: [PATCH v1 09/11] backports: use Kconfig for backport version information On Tue, 2014-11-04 at 00:43 -0800, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" <mcgrof@...e.com> > > Instead of relying on Makefile hacks just use Kconfig for > defining the variables needed. We can do this since these > variables are all known at packaging time. The exception > is BACKPORTS_GIT_TRACKED, but for that we can define a > kconfig variable which only if set will we rely on the > environment for picking it up and later exporting it through > Kconfig. Since Kconfig doesn't keep config variables defined > with option env we use a secondary config entry for that. I'd prefer you didn't do this. When we track the backports in a git tree this will mean constant changes to these files, where currently the changes are constrained to just the "versions" file. 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/
Powered by blists - more mailing lists