Searched hist:a436bb7b (Results 1 - 5 of 5) sorted by relevance
/linux-master/arch/x86/ | ||
H A D | Makefile.um | diff a436bb7b Fri Mar 27 05:43:36 MDT 2015 Masahiro Yamada <yamada.masahiro@socionext.com> kbuild: use relative path more to include Makefile 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: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Michal Marek <mmarek@suse.cz> |
H A D | Makefile | diff a436bb7b Fri Mar 27 05:43:36 MDT 2015 Masahiro Yamada <yamada.masahiro@socionext.com> kbuild: use relative path more to include Makefile 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: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Michal Marek <mmarek@suse.cz> |
/linux-master/arch/um/ | ||
H A D | Makefile | diff a436bb7b Fri Mar 27 05:43:36 MDT 2015 Masahiro Yamada <yamada.masahiro@socionext.com> kbuild: use relative path more to include Makefile 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: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Michal Marek <mmarek@suse.cz> |
/linux-master/arch/mips/ | ||
H A D | Makefile | diff a436bb7b Fri Mar 27 05:43:36 MDT 2015 Masahiro Yamada <yamada.masahiro@socionext.com> kbuild: use relative path more to include Makefile 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: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Michal Marek <mmarek@suse.cz> |
/linux-master/ | ||
H A D | Makefile | diff a436bb7b Fri Mar 27 05:43:36 MDT 2015 Masahiro Yamada <yamada.masahiro@socionext.com> kbuild: use relative path more to include Makefile 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: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Michal Marek <mmarek@suse.cz> diff a436bb7b Fri Mar 27 05:43:36 MDT 2015 Masahiro Yamada <yamada.masahiro@socionext.com> kbuild: use relative path more to include Makefile 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: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Michal Marek <mmarek@suse.cz> |
Completed in 1484 milliseconds