Intel OpenBMC Linux kernel source tree (mirror) https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=v3.16-rc4 2014-07-06T19:37:51+00:00 2014-07-06T19:37:51+00:00 Linus Torvalds torvalds@linux-foundation.org 2014-07-06T19:37:51+00:00 urn:sha1:cd3de83f147601356395b57a8673e9c5ff1e59d1 2014-07-04T01:34:00+00:00 Linus Torvalds torvalds@linux-foundation.org 2014-07-04T01:34:00+00:00 urn:sha1:af6f157a4b4f511d06d564086cb3516bb164b7c6 Pull kbuild fix from Michal Marek: "There is one more fix for the relative paths series from -rc1: Print the path to the build directory at the start of the build, so that editors and IDEs can match the relative paths to source files" * 'rc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild: kbuild: Print the name of the build directory 2014-07-03T13:25:11+00:00 Michal Marek mmarek@suse.cz 2014-07-02T12:28:26+00:00 urn:sha1:c2e28dc975ea87feed84415006ae143424912ac7 With commit 9da0763b (kbuild: Use relative path when building in a subdir of the source tree), the compiler messages include relative paths. These are however relative to the build directory, not the directory where make was started. Print the "Entering directory ..." message once, so that IDEs/editors can find the source files. Acked-by: David Howells <dhowells@redhat.com> Signed-off-by: Michal Marek <mmarek@suse.cz> 2014-06-29T21:11:36+00:00 Linus Torvalds torvalds@linux-foundation.org 2014-06-29T21:11:36+00:00 urn:sha1:4c834452aad01531db949414f94f817a86348d59 2014-06-22T05:02:54+00:00 Linus Torvalds torvalds@linux-foundation.org 2014-06-22T05:02:54+00:00 urn:sha1:a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee 2014-06-16T03:45:28+00:00 Linus Torvalds torvalds@linux-foundation.org 2014-06-16T03:45:28+00:00 urn:sha1:7171511eaec5bf23fb06078f59784a3a0626b38f 2014-06-13T04:23:38+00:00 Linus Torvalds torvalds@linux-foundation.org 2014-06-13T04:23:38+00:00 urn:sha1:1700ff823b27b6572cf4c3cec66d279baa1a5d30 Pull kbuild updates from Michal Marek: "Kbuild changes for v3.16-rc1: - cross-compilation fix so that cc-option is testing the right compiler - Fix for make defconfig all - Using relative paths to the object and source directory where possible, plus fixes for the fallout of the change - several cleanups in the Makefiles and scripts The powerpc fix is from today, because it was only discovered recently. The rest has been in linux-next for some time" * 'kbuild' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild: powerpc: Avoid circular dependency with zImage.% kbuild: create include/config directory in scripts/kconfig/Makefile kbuild: do not create include/linux directory Makefile: Fix unrecognized cross-compiler command line options kbuild: do not add "selinux" to subdir- twice um: Fix for relative objtree when generating x86 headers kbuild: Use relative path when building in a subdir of the source tree kbuild: Use relative path when building in the source tree kbuild: Use relative path for $(objtree) firmware: Use $(quote) in the Makefile firmware: Simplify directory creation kbuild: trivial - fix comment block indent kbuild: trivial - remove trailing spaces kbuild: support simultaneous "make %config" and "make all" kbuild: move extra gcc checks to scripts/Makefile.extrawarn 2014-06-09T22:20:20+00:00 Masahiro Yamada yamada.m@jp.panasonic.com 2014-05-29T05:33:03+00:00 urn:sha1:9815594a780404810c2a6280de1a268dcfcb0729 The directory include/config is used only for silentoldconfig, localmodconfig, localyesconfig. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Signed-off-by: Michal Marek <mmarek@suse.cz> 2014-06-09T22:20:12+00:00 Masahiro Yamada yamada.m@jp.panasonic.com 2014-05-29T05:33:02+00:00 urn:sha1:356db564fbdfb1aa82f9c1c842947c1e0127d12f There are no generated files under include/linux directory. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Signed-off-by: Michal Marek <mmarek@suse.cz> 2014-06-09T21:28:07+00:00 Geert Uytterhoeven geert@linux-m68k.org 2014-05-27T07:54:12+00:00 urn:sha1:a1c48bb160f8368ea9668a1ff98513631fa0d87a On architectures that setup CROSS_COMPILE in their arch/*/Makefile (arc, blackfin, m68k, mips, parisc, score, sh, tile, unicore32, xtensa), cc-option and cc-disable-warning may check against the wrong compiler, causing errors like cc1: error: unrecognized command line option "-Wno-maybe-uninitialized" if the host gcc supports a compiler option, while the cross compiler doesn't support that option. Move all logic using cc-option or cc-disable-warning below the inclusion of the arch's Makefile to fix this. Introduced by - commit e74fc973b6e531fef1fce8b101ffff05ecfb774c ("Turn off -Wmaybe-uninitialized when building with -Os"), - commit 61163efae02040f66a95c8ed17f4407951ba58fa ("kbuild: LLVMLinux: Add Kbuild support for building kernel with Clang"). As -Wno-maybe-uninitialized requires a quite recent gcc (gcc 4.6.3 on Ubuntu 12.04 LTS doesn't support it), this only showed up recently (gcc 4.8.2 on Ubuntu 14.04 LTS does support it). Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Michal Marek <mmarek@suse.cz>