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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 28 Oct 2017 23:59:59 +0900 From: Masahiro Yamada <yamada.masahiro@...ionext.com> To: Nick Desaulniers <ndesaulniers@...gle.com> Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>, Michael Davidson <md@...gle.com>, Greg Hackmann <ghackmann@...gle.com>, Pirama Arumuga Nainar <pirama@...gle.com>, Ingo Molnar <mingo@...nel.org>, Matthias Kaehlcke <mka@...omium.org>, Arnd Bergmann <arnd@...db.de>, Mark Charlebois <charlebm@...il.com>, Cao jin <caoj.fnst@...fujitsu.com>, Marcin Nowakowski <marcin.nowakowski@...tec.com>, Josh Poimboeuf <jpoimboe@...hat.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] kbuild: fix linker feature test macros when cross compiling with Clang 2017-10-28 3:28 GMT+09:00 Nick Desaulniers <ndesaulniers@...gle.com>: > + linux-kbuild@...r.kernel.org > > On Fri, Oct 27, 2017 at 4:20 AM, Masahiro Yamada > <yamada.masahiro@...ionext.com> wrote: >> I do not like to add $(CLANG_TARGET) to a place for common helpers. >> Instead of $(CLANG_TARGET), please add >> $(KBUILD_CPPFLAGS) $(CC_OPTION_CFLAGS) >> to cc-ldoption and ld-option. > > Thanks for the review. I agree that sounds like a better option. > >> I have two requests next time: >> - please include linux-kbuild@...r.kernel.org in your To list > > Sure thing. scripts/get_maintainer.pl does not recommend that list for > this file; is there a way to explicitly add that list to the > recommendation for that source file? Ah, I realized MAINTAINERS does not claim the maintainership of this file. There are so many misc scripts in scripts/, so I hesitate to add scripts/* pattern to MAINTAINERS. >> - please base your patch on linux-kbuild/kbuild branch > > Will do. Do I need to note it's based off that branch? Otherwise wont > 0-day bot complain that my patch doesn't apply/build on torvalds/linux > ? I am not sure in which case the 0-day bot complain about it. Now, I applied v2. If the bot find a problem, it will send us a report. -- Best Regards Masahiro Yamada
Powered by blists - more mailing lists