<?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>134502ab - openrisc: migrate to the generic rule for built-in DTB</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/dtc/include-prefixes/openrisc/Makefile#134502ab</link>
        <description>openrisc: migrate to the generic rule for built-in DTBCommit 654102df2ac2 (&quot;kbuild: add generic support for built-in bootDTBs&quot;) introduced generic support for built-in DTBs.Select GENERIC_BUILTIN_DTB to use the generic rule.To keep consistency across architectures, this commit also renamesCONFIG_OPENRISC_BUILTIN_DTB_NAME to CONFIG_BUILTIN_DTB_NAME.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Signed-off-by: Stafford Horne &lt;shorne@gmail.com&gt;

            List of files:
            /linux-6.15/scripts/dtc/include-prefixes/openrisc/Makefile</description>
        <pubDate>Sun, 22 Dec 2024 00:23:50 +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/scripts/dtc/include-prefixes/openrisc/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/scripts/dtc/include-prefixes/openrisc/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>74ce1896 - kbuild: clean up *.dtb and *.dtb.S patterns from top-level Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/dtc/include-prefixes/openrisc/Makefile#74ce1896</link>
        <description>kbuild: clean up *.dtb and *.dtb.S patterns from top-level MakefileWe need to add &quot;clean-files&quot; in Makfiles to clean up DT blobs, but weoften miss to do so.Since there are no source files that end with .dtb or .dtb.S, so wecan clean-up those files from the top-level Makefile.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;

            List of files:
            /linux-6.15/scripts/dtc/include-prefixes/openrisc/Makefile</description>
        <pubDate>Thu, 02 Nov 2017 02:51:25 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&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/scripts/dtc/include-prefixes/openrisc/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/scripts/dtc/include-prefixes/openrisc/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>
<item>
        <title>19fbd6b2 - openrisc: use new common dtc rule</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/scripts/dtc/include-prefixes/openrisc/Makefile#19fbd6b2</link>
        <description>openrisc: use new common dtc ruleThe current rules have the .dtb files build in a different directoryfrom the .dts files. This patch changes openrisc to use the generic dtbrule which builds .dtb files in the same directory as the source .dts.This requires renaming arch/openrisc/boot/Makefile toarch/openrisc/boot/dts/Makefile, and updating arch/openrisc/Makefile tocall the new Makefile.Cc: Jonas Bonn &lt;jonas@southpole.se&gt;Cc: linux@lists.openrisc.netSigned-off-by: Stephen Warren &lt;swarren@nvidia.com&gt;Signed-off-by: Rob Herring &lt;rob.herring@calxeda.com&gt;

            List of files:
            /linux-6.15/scripts/dtc/include-prefixes/openrisc/Makefile</description>
        <pubDate>Tue, 27 Nov 2012 23:29:13 +0000</pubDate>
        <dc:creator>Stephen Warren &lt;swarren@nvidia.com&gt;</dc:creator>
    </item>
</channel>
</rss>
