- 21 9月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 13 9月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 04 9月, 2015 1 次提交
-
-
由 Michal Marek 提交于
We cannot detect clang before including the arch Makefile, because that can set the default cross compiler. We also cannot detect clang after including the arch Makefile, because powerpc wants to know about clang. Solve this by using an deferred variable. This costs us a few shell invocations, but this is only a constant number. Reported-by: NBehan Webster <behanw@converseincode.com> Reported-by: NAnton Blanchard <anton@samba.org> Signed-off-by: NMichal Marek <mmarek@suse.com>
-
- 31 8月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 28 8月, 2015 1 次提交
-
-
由 Rasmus Villemoes 提交于
Make sure 'make clean' removes *.su files generated by the gcc option -fstack-usage. Signed-off-by: NRasmus Villemoes <linux@rasmusvillemoes.dk> Signed-off-by: NMichal Marek <mmarek@suse.com>
-
- 24 8月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 17 8月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 14 8月, 2015 2 次提交
-
-
由 David Woodhouse 提交于
Since commit 1329e8cc ("modsign: Extract signing cert from CONFIG_MODULE_SIG_KEY if needed"), the build system has carefully coped with the signing key being specified as a relative path in either the source or or the build trees. However, the actual signing of modules has not worked if the filename is relative to the source tree. Fix that by moving the config_filename helper into scripts/Kbuild.include so that it can be used from elsewhere, and then using it in the top-level Makefile to find the signing key file. Kill the intermediate $(MODPUBKEY) and $(MODSECKEY) variables too, while we're at it. There's no need for them. Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com> Signed-off-by: NDavid Howells <dhowells@redhat.com>
-
由 David Howells 提交于
Move certificate handling out of the kernel/ directory and into a certs/ directory to get all the weird stuff in one place and move the generated signing keys into this directory. Signed-off-by: NDavid Howells <dhowells@redhat.com> Reviewed-by: NDavid Woodhouse <David.Woodhouse@intel.com>
-
- 10 8月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 07 8月, 2015 3 次提交
-
-
由 David Woodhouse 提交于
The current rule for generating signing_key.priv and signing_key.x509 is a classic example of a bad rule which has a tendency to break parallel make. When invoked to create *either* target, it generates the other target as a side-effect that make didn't predict. So let's switch to using a single file signing_key.pem which contains both key and certificate. That matches what we do in the case of an external key specified by CONFIG_MODULE_SIG_KEY anyway, so it's also slightly cleaner. Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com> Signed-off-by: NDavid Howells <dhowells@redhat.com>
-
由 David Woodhouse 提交于
Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com> Signed-off-by: NDavid Howells <dhowells@redhat.com>
-
由 David Howells 提交于
Move to using PKCS#7 messages as module signatures because: (1) We have to be able to support the use of X.509 certificates that don't have a subjKeyId set. We're currently relying on this to look up the X.509 certificate in the trusted keyring list. (2) PKCS#7 message signed information blocks have a field that supplies the data required to match with the X.509 certificate that signed it. (3) The PKCS#7 certificate carries fields that specify the digest algorithm used to generate the signature in a standardised way and the X.509 certificates specify the public key algorithm in a standardised way - so we don't need our own methods of specifying these. (4) We now have PKCS#7 message support in the kernel for signed kexec purposes and we can make use of this. To make this work, the old sign-file script has been replaced with a program that needs compiling in a previous patch. The rules to build it are added here. Signed-off-by: NDavid Howells <dhowells@redhat.com> Tested-by: NVivek Goyal <vgoyal@redhat.com>
-
- 03 8月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 27 7月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 22 7月, 2015 2 次提交
-
-
由 Jason A. Donenfeld 提交于
Running `make modules_install` ordinarily will overwrite existing modules. This is the desired behavior, and is how pretty much every other `make install` target works. However, if CONFIG_MODULE_COMPRESS is enabled, modules are passed through gzip and xz which then do the file writing. Both gzip and xz will error out if the file already exists, unless -f is passed. This patch adds -f so that the behavior is uniform. Signed-off-by: NJason A. Donenfeld <Jason@zx2c4.com> Signed-off-by: NMichal Marek <mmarek@suse.com>
-
由 Michal Marek 提交于
Initialize the ARCH_* overrides before including the arch Makefile, to avoid picking up the values from the environment. The variables can still be overriden on the make command line, but this won't happen by accident. Signed-off-by: NMichal Marek <mmarek@suse.com>
-
- 20 7月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 13 7月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 06 7月, 2015 2 次提交
-
-
由 Michal Marek 提交于
Since commit a1c48bb1 (Makefile: Fix unrecognized cross-compiler command line options), the arch Makefile is included earlier by the main Makefile, preventing the arc architecture to set its -O3 compiler option. Since there might be more use cases for an arch Makefile to fine-tune the options, add support for ARCH_CPPFLAGS, ARCH_AFLAGS and ARCH_CFLAGS variables that are appended to the respective kbuild variables. The user still has the final say via the KCPPFLAGS, KAFLAGS and KCFLAGS variables. Reported-by: NVineet Gupta <Vineet.Gupta1@synopsys.com> Cc: stable@vger.kernel.org # 3.16+ Signed-off-by: NMichal Marek <mmarek@suse.com>
-
由 Linus Torvalds 提交于
-
- 22 6月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 15 6月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 08 6月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 01 6月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 25 5月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 19 5月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 11 5月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 04 5月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 29 4月, 2015 1 次提交
-
-
由 Jiri Olsa 提交于
Several fixes were needed to allow following builds: $ make tools/tmon $ make -C <kernelsrc> tools/perf $ make -C <kernelsrc>/tools perf - some of the tools (perf) use same make variables as in kernel build, unsetting srctree and objtree - using original $(O) for O variable - perf build does not follow the descend function setup invoking it via it's own make rule I tried the rest of the tools/Makefile targets and they seem to work now. Reported-by: NBrian Norris <computersforpeace@gmail.com> Signed-off-by: NJiri Olsa <jolsa@kernel.org> Cc: Borislav Petkov <bp@suse.de> Cc: Brian Norris <computersforpeace@gmail.com> Cc: David Ahern <dsahern@gmail.com> Cc: David Howells <dhowells@redhat.com> Cc: Michal Marek <mmarek@suse.cz> Cc: Namhyung Kim <namhyung@kernel.org> Cc: Paul Mackerras <paulus@samba.org> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Sam Ravnborg <sam@ravnborg.org> Cc: linux-kbuild@vger.kernel.org Link: http://lkml.kernel.org/r/1429389280-18720-3-git-send-email-jolsa@kernel.orgSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
-
- 27 4月, 2015 2 次提交
-
-
由 Paul Cercueil 提交于
When the host's C compiler is clang, and when attempting to cross-compile Linux e.g. to MIPS with mipsel-linux-gcc, the Makefile would incorrectly detect the use of clang, which resulted in clang-specific flags being passed to mipsel-linux-gcc. This can be verified under Debian by installing the "clang" package, and then using it as the default compiler with: sudo update-alternatives --config cc This patch moves the detection of clang after the $(CC) variable is initialized to the name of the cross-compiler, so that the check applies to the cross-compiler and not the host's C compiler. v2: Move the detection of clang after the inclusion of the arch/*/Makefile (as they might set $(CROSS_COMPILE)) Signed-off-by: NPaul Cercueil <paul@crapouillou.net> Signed-off-by: NMichal Marek <mmarek@suse.cz>
-
由 Linus Torvalds 提交于
-
- 13 4月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 09 4月, 2015 1 次提交
-
-
由 Anton Blanchard 提交于
To use jump labels in assembly we need the HAVE_JUMP_LABEL define, so we select a fallback version if the toolchain does not support them. Modify linux/jump_label.h so it can be included by assembly files. We also need to add -DCC_HAVE_ASM_GOTO to KBUILD_AFLAGS. Signed-off-by: NAnton Blanchard <anton@samba.org> Acked-by: NPeter Zijlstra (Intel) <peterz@infradead.org> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: benh@kernel.crashing.org Cc: catalin.marinas@arm.com Cc: davem@davemloft.net Cc: heiko.carstens@de.ibm.com Cc: jbaron@akamai.com Cc: linux@arm.linux.org.uk Cc: linuxppc-dev@lists.ozlabs.org Cc: liuj97@gmail.com Cc: mgorman@suse.de Cc: mmarek@suse.cz Cc: mpe@ellerman.id.au Cc: paulus@samba.org Cc: ralf@linux-mips.org Cc: rostedt@goodmis.org Cc: schwidefsky@de.ibm.com Cc: will.deacon@arm.com Link: http://lkml.kernel.org/r/1428551492-21977-2-git-send-email-anton@samba.orgSigned-off-by: NIngo Molnar <mingo@kernel.org>
-
- 07 4月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 02 4月, 2015 1 次提交
-
-
由 Masahiro Yamada 提交于
Prior to this commit, it was impossible to use relative path to include Makefiles from the top level Makefile because the option "--include-dir=$(srctree)" becomes effective when Make enters into sub Makefiles. To use relative path in any places, this commit moves the option above the "sub-make" target. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: NMichal Marek <mmarek@suse.cz>
-
- 30 3月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 25 3月, 2015 1 次提交
-
-
由 Masahiro Yamada 提交于
Enough time has passed since "make depend" was deprecated. Nobody would be in trouble without this hint. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Signed-off-by: NMichal Marek <mmarek@suse.cz>
-
- 23 3月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-
- 16 3月, 2015 1 次提交
-
-
由 Linus Torvalds 提交于
-