<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>083cad78 - kbuild: fix &quot;cat: .version: No such file or directory&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#083cad78</link>
        <description>kbuild: fix &quot;cat: .version: No such file or directory&quot;Since commit 2df8220cc511 (&quot;kbuild: build init/built-in.a just once&quot;),the .version file is not touched at all when KBUILD_BUILD_VERSION isgiven.If KBUILD_BUILD_VERSION is specified and the .version file is missing(for example right after &apos;make mrproper&apos;), &quot;No such file or director&quot;is shown. Even if the .version exists, it is irrelevant to the versionof the current build.  $ make -j$(nproc) KBUILD_BUILD_VERSION=100 mrproper defconfig all    [ snip ]    BUILD   arch/x86/boot/bzImage  cat: .version: No such file or directory  Kernel: arch/x86/boot/bzImage is ready  (#)Show KBUILD_BUILD_VERSION if it is given.Fixes: 2df8220cc511 (&quot;kbuild: build init/built-in.a just once&quot;)Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Reviewed-by: Nicolas Schier &lt;nicolas@fjasle.eu&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Tue, 22 Nov 2022 14:39:02 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>ce697cce - kbuild: remove head-y syntax</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#ce697cce</link>
        <description>kbuild: remove head-y syntaxKbuild puts the objects listed in head-y at the head of vmlinux.Conventionally, we do this for head*.S, which contains the kernel entrypoint.A counter approach is to control the section order by the linker script.Actually, the code marked as __HEAD goes into the &quot;.head.text&quot; section,which is placed before the normal &quot;.text&quot; section.I do not know if both of them are needed. From the build systemperspective, head-y is not mandatory. If you can achieve the proper codeplacement by the linker script only, it would be cleaner.I collected the current head-y objects into head-object-list.txt. It isa whitelist. My hope is it will be reduced in the long run.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Tested-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;Reviewed-by: Nicolas Schier &lt;nicolas@fjasle.eu&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Sat, 24 Sep 2022 18:19:15 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>c0ee9bba - microblaze: use built-in function to get CPU_{MAJOR,MINOR,REV}</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#c0ee9bba</link>
        <description>microblaze: use built-in function to get CPU_{MAJOR,MINOR,REV}Use built-in functions instead of shell commands to avoid forkingprocesses.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Reviewed-by: Nicolas Schier &lt;n.schier@avm.de&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Tue, 14 Dec 2021 02:53:55 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>129ab0d2 - kbuild: do not quote string values in include/config/auto.conf</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#129ab0d2</link>
        <description>kbuild: do not quote string values in include/config/auto.confThe previous commit fixed up all shell scripts to not includeinclude/config/auto.conf.Now that include/config/auto.conf is only included by Makefiles,we can change it into a more Make-friendly form.Previously, Kconfig output string values enclosed with double-quotes(both in the .config and include/config/auto.conf):    CONFIG_X=&quot;foo bar&quot;Unlike shell, Make handles double-quotes (and single-quotes as well)verbatim. We must rip them off when used.There are some patterns:  [1] $(patsubst &quot;%&quot;,%,$(CONFIG_X))  [2] $(CONFIG_X:&quot;%&quot;=%)  [3] $(subst &quot;,,$(CONFIG_X))  [4] $(shell echo $(CONFIG_X))These are not only ugly, but also fragile.[1] and [2] do not work if the value contains spaces, like   CONFIG_X=&quot; foo bar &quot;[3] does not work correctly if the value contains double-quotes like   CONFIG_X=&quot;foo\&quot;bar&quot;[4] seems to work better, but has a cost of forking a process.Anyway, quoted strings were always PITA for our Makefiles.This commit changes Kconfig to stop quoting in include/config/auto.conf.These are the string type symbols referenced in Makefiles or scripts:    ACPI_CUSTOM_DSDT_FILE    ARC_BUILTIN_DTB_NAME    ARC_TUNE_MCPU    BUILTIN_DTB_SOURCE    CC_IMPLICIT_FALLTHROUGH    CC_VERSION_TEXT    CFG80211_EXTRA_REGDB_KEYDIR    EXTRA_FIRMWARE    EXTRA_FIRMWARE_DIR    EXTRA_TARGETS    H8300_BUILTIN_DTB    INITRAMFS_SOURCE    LOCALVERSION    MODULE_SIG_HASH    MODULE_SIG_KEY    NDS32_BUILTIN_DTB    NIOS2_DTB_SOURCE    OPENRISC_BUILTIN_DTB    SOC_CANAAN_K210_DTB_SOURCE    SYSTEM_BLACKLIST_HASH_LIST    SYSTEM_REVOCATION_KEYS    SYSTEM_TRUSTED_KEYS    TARGET_CPU    UNUSED_KSYMS_WHITELIST    XILINX_MICROBLAZE0_FAMILY    XILINX_MICROBLAZE0_HW_VER    XTENSA_VARIANT_NAMEI checked them one by one, and fixed up the code where necessary.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Tue, 14 Dec 2021 02:53:53 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>8212f898 - kbuild: use more subdir- for visiting subdirectories while cleaning</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#8212f898</link>
        <description>kbuild: use more subdir- for visiting subdirectories while cleaningDocumentation/kbuild/makefiles.rst suggests to use &quot;archclean&quot; forcleaning arch/$(SRCARCH)/boot/, but it is not a hard requirement.Since commit d92cc4d51643 (&quot;kbuild: require all architectures to havearch/$(SRCARCH)/Kbuild&quot;), we can use the &quot;subdir- += boot&quot; trick forall architectures. This can take advantage of the parallel option (-j)for &quot;make clean&quot;.I also cleaned up the comments in arch/$(SRCARCH)/Makefile. The &quot;archdep&quot;target no longer exists.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;Acked-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt; (powerpc)

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Wed, 13 Oct 2021 06:36:22 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>31551116 - microblaze: move core-y in arch/microblaze/Makefile to arch/microblaze/Kbuild</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#31551116</link>
        <description>microblaze: move core-y in arch/microblaze/Makefile to arch/microblaze/KbuildUse obj-y to clean up Makefile.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Link: https://lore.kernel.org/r/20210811164518.187497-1-masahiroy@kernel.orgSigned-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Wed, 11 Aug 2021 16:45:18 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>14a83249 - arch: microblaze: Fix spelling mistake &quot;vesion&quot; -&gt; &quot;version&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#14a83249</link>
        <description>arch: microblaze: Fix spelling mistake &quot;vesion&quot; -&gt; &quot;version&quot;There is a spelling mistake in the comment. Fix it.Signed-off-by: Colin Ian King &lt;colin.king@canonical.com&gt;Link: https://lore.kernel.org/r/20210601103707.9701-1-colin.king@canonical.comSigned-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Tue, 01 Jun 2021 10:37:07 +0000</pubDate>
        <dc:creator>Colin Ian King &lt;colin.king@canonical.com&gt;</dc:creator>
    </item>
<item>
        <title>d897a167 - arch: microblaze: Remove CONFIG_OPROFILE support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#d897a167</link>
        <description>arch: microblaze: Remove CONFIG_OPROFILE supportThe &quot;oprofile&quot; user-space tools don&apos;t use the kernel OPROFILE supportany more, and haven&apos;t in a long time. User-space has been converted tothe perf interfaces.Remove the old oprofile&apos;s architecture specific support.Suggested-by: Christoph Hellwig &lt;hch@infradead.org&gt;Suggested-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Signed-off-by: Viresh Kumar &lt;viresh.kumar@linaro.org&gt;Acked-by: Robert Richter &lt;rric@kernel.org&gt;Acked-by: Michal Simek &lt;michal.simek@xilinx.com&gt;Acked-by: William Cohen &lt;wcohen@redhat.com&gt;Acked-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Thu, 14 Jan 2021 11:35:20 +0000</pubDate>
        <dc:creator>Viresh Kumar &lt;viresh.kumar@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>05cdf457 - microblaze: Remove noMMU code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#05cdf457</link>
        <description>microblaze: Remove noMMU codeThis configuration is obsolete and likely none is really using it. That&apos;swhy remove it to simplify code.Note about CONFIG_MMU in hw_exception_handler.S is left intentionallyfor better comment understanding.Cc: Mike Rapoport &lt;rppt@kernel.org&gt;Cc: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;Acked-by: Mike Rapoport &lt;rppt@linux.ibm.com&gt;Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://lore.kernel.org/r/43486cab370e0c0a79860120b71e0caac75a7e44.1606397528.git.michal.simek@xilinx.com

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Thu, 26 Nov 2020 13:32:25 +0000</pubDate>
        <dc:creator>Michal Simek &lt;michal.simek@xilinx.com&gt;</dc:creator>
    </item>
<item>
        <title>52e79c4f - microblaze: fix race condition in building boot images</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#52e79c4f</link>
        <description>microblaze: fix race condition in building boot imagesI fixed a race condition in the parallel building of ARM in commit3939f3345050 (&quot;ARM: 8418/1: add boot image dependencies to notgenerate invalid images&quot;).I see the same problem for MicroBlaze too.&quot;make -j&lt;N&gt; ARCH=microblaze all linux.bin.ub&quot; results in a broken buildbecause two threads descend into arch/microblaze/boot simultaneously.Add proper dependencies to avoid it.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Fri, 07 Dec 2018 11:33:56 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>3dda563b - microblaze: add linux.bin* and simpleImage.* to PHONY</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#3dda563b</link>
        <description>microblaze: add linux.bin* and simpleImage.* to PHONYlinux.bin, linux.bin.gz, and linux.bin.ub are phony targets togenerate a corresponding image under arch/microblaze/boot/.simpleImage.% also works like a phony target, but a pattern thatcontains &apos;%&apos; cannot be a phony target. I replaced it with equivalentsimpleImage.$(DTB).Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Fri, 07 Dec 2018 11:33:55 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>4722a3e6 - microblaze: fix multiple bugs in arch/microblaze/boot/Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#4722a3e6</link>
        <description>microblaze: fix multiple bugs in arch/microblaze/boot/MakefileThis commit fixes some build issues.The first issue is the breakage of linux.bin.ub target since commitece97f3a5fb5 (&quot;microblaze: Fix simpleImage format generation&quot;)because the addition of UIMAGE_{IN,OUT} affected it.make ARCH=microblaze CROSS_COMPILE=microblaze-linux- linux.bin.ub  [ snip ]  OBJCOPY arch/microblaze/boot/linux.bin  UIMAGE  arch/microblaze/boot/linux.bin.ub.ub/usr/bin/mkimage: Can&apos;t open arch/microblaze/boot/linux.bin.ub: No such file or directorymake[1]: *** [arch/microblaze/boot/Makefile;14: arch/microblaze/boot/linux.bin.ub] Error 1make: *** [arch/microblaze/Makefile;83: linux.bin.ub] Error 2The second issue is the use of the &quot;if_changed&quot; multiple times forthe same target.As commit 92a4728608a8 (&quot;x86/boot: Fix if_changed build flip/flop bug&quot;)pointed out, this never works properly. Moreover, generating multipleimages as a side-effect is confusing.Let&apos;s split the build recipe for each image.simpleImage.&lt;dt&gt;*.unstrip is just a copy of vmlinux.simpleImage.&lt;dt&gt; and simpleImage.&lt;dt&gt;.ub are created in the same wayas linux.bin and linux.bin.ub, respectively.I kept simpleImage.* recipes independent of linux.bin.* ones to notchange the behavior.Lastly, this commit fixes &quot;make ARCH=microblaze clean&quot;. Previously,it only cleaned up the unstrip image. Now, all the simpleImage filesare cleaned.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Fri, 07 Dec 2018 11:33:54 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>2e14f94c - microblaze: move &quot;... is ready&quot; messages to arch/microblaze/Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#2e14f94c</link>
        <description>microblaze: move &quot;... is ready&quot; messages to arch/microblaze/MakefileTo prepare for more fixes, move this to arch/microblaze/Makefile.Otherwise, the same &quot;... is ready&quot; would be printed multiple times.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Fri, 07 Dec 2018 11:33:53 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>bafcc61d - microblaze: adjust the help to the real behavior</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#bafcc61d</link>
        <description>microblaze: adjust the help to the real behavior&quot;make ARCH=microblaze help&quot; mentions simpleImage.&lt;dt&gt;.unstrip,but it is not a real Make target. It does not work because Makefileassumes &quot;system.unstrip&quot; is the name of DT.$ make ARCH=microblaze CROSS_COMPILE=microblaze-linux- simpleImage.system.unstrip  [ snip ]make[1]: *** No rule to make target &apos;arch/microblaze/boot/dts/system.unstrip.dtb&apos;, needed by &apos;arch/microblaze/boot/dts/system.dtb&apos;.  Stop.make: *** [Makefile;1060: arch/microblaze/boot/dts] Error 2make: *** Waiting for unfinished jobs....simpleImage.&lt;dt&gt; works like a phony target that generates multipleimages. Reflect the real behavior. I removed the DT directory pathinformation because it is already explained a few lines below.While I am here, I deleted the redundant *_defconfig explanation.The top-level Makefile caters to list available defconfig files:  mmu_defconfig            - Build for mmu  nommu_defconfig          - Build for nommuSigned-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Fri, 07 Dec 2018 11:33:52 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>1e17ab53 - microblaze: generate uapi header and system call table files</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#1e17ab53</link>
        <description>microblaze: generate uapi header and system call table filesSystem call table generation script must be run to gener-ate unistd_32.h and syscall_table.h files. This patch willhave changes which will invokes the script.This patch will generate unistd_32.h and syscall_table.hfiles by the syscall table generation script invoked bymicroblaze/Makefile and the generated files against theremoved files must be identical.The generated uapi header file will be included in uapi/-asm/unistd.h and generated system call table header filewill be included by kernel/syscall_table.S file.Signed-off-by: Firoz Khan &lt;firoz.khan@linaro.org&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Tue, 13 Nov 2018 06:04:34 +0000</pubDate>
        <dc:creator>Firoz Khan &lt;firoz.khan@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>37c8a5fa - kbuild: consolidate Devicetree dtb build rules</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#37c8a5fa</link>
        <description>kbuild: consolidate Devicetree dtb build rulesThere is nothing arch specific about building dtb files other than theirlocation under /arch/*/boot/dts/. Keeping each arch aligned is a pain.The dependencies and supported targets are all slightly different.Also, a cross-compiler for each arch is needed, but really the hostcompiler preprocessor is perfectly fine for building dtbs. Move thebuild rules to a common location and remove the arch specific ones. Thisis done in a single step to avoid warnings about overriding rules.The build dependencies had been a mixture of &apos;scripts&apos; and/or &apos;prepare&apos;.These pull in several dependencies some of which need a target compiler(specifically devicetable-offsets.h) and aren&apos;t needed to build dtbs.All that is really needed is dtc, so adjust the dependencies to only bedtc.This change enables support &apos;dtbs_install&apos; on some arches which weremissing the target.Acked-by: Will Deacon &lt;will.deacon@arm.com&gt;Acked-by: Paul Burton &lt;paul.burton@mips.com&gt;Acked-by: Ley Foon Tan &lt;ley.foon.tan@intel.com&gt;Acked-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Cc: Michal Marek &lt;michal.lkml@markovi.net&gt;Cc: Vineet Gupta &lt;vgupta@synopsys.com&gt;Cc: Russell King &lt;linux@armlinux.org.uk&gt;Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Cc: Yoshinori Sato &lt;ysato@users.sourceforge.jp&gt;Cc: Michal Simek &lt;monstr@monstr.eu&gt;Cc: Ralf Baechle &lt;ralf@linux-mips.org&gt;Cc: James Hogan &lt;jhogan@kernel.org&gt;Cc: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;Cc: Paul Mackerras &lt;paulus@samba.org&gt;Cc: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Cc: Chris Zankel &lt;chris@zankel.net&gt;Cc: Max Filippov &lt;jcmvbkbc@gmail.com&gt;Cc: linux-kbuild@vger.kernel.orgCc: linux-snps-arc@lists.infradead.orgCc: linux-arm-kernel@lists.infradead.orgCc: uclinux-h8-devel@lists.sourceforge.jpCc: linux-mips@linux-mips.orgCc: nios2-dev@lists.rocketboards.orgCc: linuxppc-dev@lists.ozlabs.orgCc: linux-xtensa@linux-xtensa.orgSigned-off-by: Rob Herring &lt;robh@kernel.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Wed, 10 Jan 2018 21:19:37 +0000</pubDate>
        <dc:creator>Rob Herring &lt;robh@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>d503ac53 - kbuild: rename LDFLAGS to KBUILD_LDFLAGS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#d503ac53</link>
        <description>kbuild: rename LDFLAGS to KBUILD_LDFLAGSCommit a0f97e06a43c (&quot;kbuild: enable &apos;make CFLAGS=...&apos; to addadditional options to CC&quot;) renamed CFLAGS to KBUILD_CFLAGS.Commit 222d394d30e7 (&quot;kbuild: enable &apos;make AFLAGS=...&apos; to addadditional options to AS&quot;) renamed AFLAGS to KBUILD_AFLAGS.Commit 06c5040cdb13 (&quot;kbuild: enable &apos;make CPPFLAGS=...&apos; to addadditional options to CPP&quot;) renamed CPPFLAGS to KBUILD_CPPFLAGS.For some reason, LDFLAGS was not renamed.Using a well-known variable like LDFLAGS may result in accidentaloverride of the variable.Kbuild generally uses KBUILD_ prefixed variables for the internallyappended options, so here is one more conversion to sanitize thenaming convention.I did not touch Makefiles under tools/ since the tools build systemis a different world.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Acked-by: Kirill A. Shutemov &lt;kirill.shutemov@linux.intel.com&gt;Reviewed-by: Palmer Dabbelt &lt;palmer@sifive.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Thu, 23 Aug 2018 23:20:39 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>0fbe9a24 - microblaze: add endianness options to LDFLAGS instead of LD</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#0fbe9a24</link>
        <description>microblaze: add endianness options to LDFLAGS instead of LDWith the recent syntax extension, Kconfig is now able to evaluate thecompiler / toolchain capability.However, accumulating flags to &apos;LD&apos; is not compatible with the wayit works; &apos;LD&apos; must be passed to Kconfig to call $(ld-option,...)from Kconfig files.  If you tweak &apos;LD&apos; in arch Makefile depending onCONFIG_CPU_BIG_ENDIAN, this would end up with circular dependencybetween Makefile and Kconfig.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Tue, 03 Jul 2018 01:22:01 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>71e7673d - microblaze: fix endian handling</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#71e7673d</link>
        <description>microblaze: fix endian handlingBuilding an allmodconfig kernel fails horribly because ofendian mismatch. It turns out that the -mlittle-endianswitch was not honored at all as we were using the wrongKconfig symbol and failing to apply CPUFLAGS to the CFLAGS.Finally, the linker flags did not get set right.This addresses all three of those issues, which now letsme build both big-endian and little-endian kernels fortesting.Fixes: 428dbf156cc5 (&quot;arch: change default endian for microblaze&quot;)Fixes: 206d3642d8ee (&quot;arch/microblaze: add choice for endianness and update Makefile&quot;)Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Tue, 02 Jan 2018 11:47:19 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/Makefile#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
</channel>
</rss>
