<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/Makefile, branch dev-5.0</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.0</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.0'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2019-05-08T05:23:00+00:00</updated>
<entry>
<title>Linux 5.0.14</title>
<updated>2019-05-08T05:23:00+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-05-08T05:23:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=274ede3e1a5fb3d0fd33acafb08993e95972c51f'/>
<id>urn:sha1:274ede3e1a5fb3d0fd33acafb08993e95972c51f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Linux 5.0.13</title>
<updated>2019-05-05T12:43:41+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-05-05T12:43:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e5b9547b1aa39164a8df1d01f2996391c0356d71'/>
<id>urn:sha1:e5b9547b1aa39164a8df1d01f2996391c0356d71</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Linux 5.0.12</title>
<updated>2019-05-04T07:21:23+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-05-04T07:21:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=6006d5b025224f2db8751d317e2e6bcdad69d4b6'/>
<id>urn:sha1:6006d5b025224f2db8751d317e2e6bcdad69d4b6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>kbuild: skip parsing pre sub-make code for recursion</title>
<updated>2019-05-04T07:21:20+00:00</updated>
<author>
<name>Masahiro Yamada</name>
<email>yamada.masahiro@socionext.com</email>
</author>
<published>2019-03-26T04:02:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c6d02b1ea4d7c58e3f631d4bc7b5287b3f72ca53'/>
<id>urn:sha1:c6d02b1ea4d7c58e3f631d4bc7b5287b3f72ca53</id>
<content type='text'>
[ Upstream commit 221cc2d27ddc49b3e06d4637db02bf78e70c573c ]

When Make recurses to the top Makefile with sub-make-done unset,
the code block surrounded by 'ifneq ($(sub-make-done),1) ... endif'
is parsed multiple times. This happens for in-tree building of
include/config/auto.conf, *-pkg, etc. with GNU Make 4.x.

This is a slight regression by commit 688931a5ad4e ("kbuild: skip
sub-make for in-tree build with GNU Make 4.x") in terms of performance
since that code block contains one $(shell ...) invocation.

Fix it by exporting the variable irrespective of sub-make being run.
I renamed it because GNU Make cannot properly export variables
containing hyphens. This is probably a bug of GNU Make, and the issue
in Kbuild had already been reported by commit 2bfbe7881ee0 ("kbuild:
Do not use hyphen in exported variable name").

Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
Signed-off-by: Sasha Levin (Microsoft) &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>Linux 5.0.11</title>
<updated>2019-05-02T08:02:58+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-05-02T08:02:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=d5a2675b207d3b3629edb3e1588ccc4f8dfb5040'/>
<id>urn:sha1:d5a2675b207d3b3629edb3e1588ccc4f8dfb5040</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Linux 5.0.10</title>
<updated>2019-04-27T07:37:45+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-04-27T07:37:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=d3da1f09fff27b3ae5908119dab312b9baec09e0'/>
<id>urn:sha1:d3da1f09fff27b3ae5908119dab312b9baec09e0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert "kbuild: use -Oz instead of -Os when using clang"</title>
<updated>2019-04-27T07:37:44+00:00</updated>
<author>
<name>Matthias Kaehlcke</name>
<email>mka@chromium.org</email>
</author>
<published>2019-04-23T19:04:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=fb9693679feb5e3fa9c983ec35dfa068a9ad83af'/>
<id>urn:sha1:fb9693679feb5e3fa9c983ec35dfa068a9ad83af</id>
<content type='text'>
commit a75bb4eb9e565b9f5115e2e8c07377ce32cbe69a upstream.

The clang option -Oz enables *aggressive* optimization for size,
which doesn't necessarily result in smaller images, but can have
negative impact on performance. Switch back to the less aggressive
-Os.

This reverts commit 6748cb3c299de1ffbe56733647b01dbcc398c419.

Suggested-by: Peter Zijlstra &lt;peterz@infradead.org&gt;
Signed-off-by: Matthias Kaehlcke &lt;mka@chromium.org&gt;
Reviewed-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;
Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
Signed-off-by: Nathan Chancellor &lt;natechancellor@gmail.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>Linux 5.0.9</title>
<updated>2019-04-20T07:17:05+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-04-20T07:17:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e4abcebedac3415cf347e95749209a4a7b6f3074'/>
<id>urn:sha1:e4abcebedac3415cf347e95749209a4a7b6f3074</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Linux 5.0.8</title>
<updated>2019-04-17T06:39:54+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-04-17T06:39:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=0b9132ee742999aee13e6b22ef7723b6d4a0eaca'/>
<id>urn:sha1:0b9132ee742999aee13e6b22ef7723b6d4a0eaca</id>
<content type='text'>
</content>
</entry>
<entry>
<title>kbuild: clang: choose GCC_TOOLCHAIN_DIR not on LD</title>
<updated>2019-04-17T06:39:44+00:00</updated>
<author>
<name>Nick Desaulniers</name>
<email>ndesaulniers@google.com</email>
</author>
<published>2019-02-11T19:30:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=622902df9ebad35413067e19bd3099f53b203d66'/>
<id>urn:sha1:622902df9ebad35413067e19bd3099f53b203d66</id>
<content type='text'>
[ Upstream commit ad15006cc78459d059af56729c4d9bed7c7fd860 ]

This causes an issue when trying to build with `make LD=ld.lld` if
ld.lld and the rest of your cross tools aren't in the same directory
(ex. /usr/local/bin) (as is the case for Android's build system), as the
GCC_TOOLCHAIN_DIR then gets set based on `which $(LD)` which will point
where LLVM tools are, not GCC/binutils tools are located.

Instead, select the GCC_TOOLCHAIN_DIR based on another tool provided by
binutils for which LLVM does not provide a substitute for, such as
elfedit.

Fixes: 785f11aa595b ("kbuild: Add better clang cross build support")
Link: https://github.com/ClangBuiltLinux/linux/issues/341
Suggested-by: Nathan Chancellor &lt;natechancellor@gmail.com&gt;
Reviewed-by: Nathan Chancellor &lt;natechancellor@gmail.com&gt;
Tested-by: Nathan Chancellor &lt;natechancellor@gmail.com&gt;
Signed-off-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;
Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
</feed>
