| 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
| ||
|
Date: Wed, 14 Sep 2011 03:48:35 +0200 From: Michal Marek <mmarek@...e.cz> To: Arnaud Lacombe <lacombar@...il.com> Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org Subject: Re: [RFC] Kbuild: allow code re-use across different directories Dne 13.9.2011 23:13, Arnaud Lacombe napsal(a): > 2011/9/9 Michal Marek <mmarek@...e.cz>: >> On 20.8.2011 02:37, Arnaud Lacombe wrote: >>> With the attached patch, we would do: >>> >>> arch/foo/boot/Makefile: >>> LDFLAGS_fancy.o := -DPANTS=30 >>> obj-y += fancy.o >>> vpath-y += $(srctree)/arch/foo/lib >>> >>> and let GNU make do the job. >> >> I like this. The only issue I can think of right now, is that if you add >> a large directory to vpath-y, then it would be easy to accidentally >> reuse more files from that directory than intended. But that could be >> easily prevented by isolating those reusable source files. >> > I do not think it is that dangerous. We enforce unique access to VPATH > and we still prioritize $(src) over any other specified path. > > That said, what would you want to pull the patch into -next, beside > kernel.org being up ? Just post it with a proper signoff. But there won't be any linux-next until kernel.org is back again. Michal -- 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