<?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>5ad0c8e4 - selftests: sync: Fix incorrect kernel headers search path</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#5ad0c8e4</link>
        <description>selftests: sync: Fix incorrect kernel headers search pathUse $(KHDR_INCLUDES) as lookup path for kernel headers. This preventsbuilding against kernel headers from the build environment in scenarioswhere kernel headers are installed into a specific output directory(O=...).Signed-off-by: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;Cc: Shuah Khan &lt;shuah@kernel.org&gt;Cc: linux-kselftest@vger.kernel.orgCc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: &lt;stable@vger.kernel.org&gt;  # 5.18+Acked-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Fri, 27 Jan 2023 13:57:47 +0000</pubDate>
        <dc:creator>Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;</dc:creator>
    </item>
<item>
        <title>b2c93e30 - selftests: sync: missing CFLAGS while compiling</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#b2c93e30</link>
        <description>selftests: sync: missing CFLAGS while compilingBased on patch: https://patchwork.kernel.org/patch/10042045/arch64-linux-gnu-gcc -c sync.c -o sync/sync.osync.c:42:29: fatal error: linux/sync_file.h: No such file or directory #include &lt;linux/sync_file.h&gt;                             ^CFLAGS is not used during the compile step, so the system instead ofkernel headers are used.  Fix this by adding CFLAGS to the OBJS compilerule.Reported-by: Lei Yang &lt;Lei.Yang@windriver.com&gt;Signed-off-by: Anders Roxell &lt;anders.roxell@linaro.org&gt;Signed-off-by: Daniel D&#237;az &lt;daniel.diaz@linaro.org&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Tue, 06 Feb 2018 22:23:39 +0000</pubDate>
        <dc:creator>Anders Roxell &lt;anders.roxell@linaro.org&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/tools/testing/selftests/sync/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/tools/testing/selftests/sync/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>b2fc6ade - selftests: sync: kselftest and kselftest-clean fail for make O=dir case</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#b2fc6ade</link>
        <description>selftests: sync: kselftest and kselftest-clean fail for make O=dir casesync test fails to build when object directory is specified to relocateobject files. Fix it to specify the correct path. Fix clean target toremove objects. Also include simplified logic to use TEST_CUSTOM_PROGSin build and clean targets instead of hard-coding the test name eachtime.Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Mon, 11 Sep 2017 20:14:41 +0000</pubDate>
        <dc:creator>Shuah Khan &lt;shuahkh@osg.samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>38f72518 - selftests: sync: use TEST_CUSTOM_PROGS instead of TEST_PROGS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#38f72518</link>
        <description>selftests: sync: use TEST_CUSTOM_PROGS instead of TEST_PROGSlib.mk var TEST_CUSTOM_PROGS is for tests that need custom buildrules. TEST_PROGS is used for test shell scripts. Fix it to useTEST_CUSTOM_PROGS. lib.mk will run and install them.Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Mon, 11 Sep 2017 19:46:44 +0000</pubDate>
        <dc:creator>Shuah Khan &lt;shuahkh@osg.samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>8ab02e09 - selftests: sync: override clean in lib.mk to fix warnings</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#8ab02e09</link>
        <description>selftests: sync: override clean in lib.mk to fix warningsAdd override with EXTRA_CLEAN for lib.mk clean to fix the followingwarnings from clean target run.Makefile:24: warning: overriding recipe for target &apos;clean&apos;../lib.mk:55: warning: ignoring old recipe for target &apos;clean&apos;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Fri, 21 Apr 2017 22:25:25 +0000</pubDate>
        <dc:creator>Shuah Khan &lt;shuahkh@osg.samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>499a1d11 - selftest: sync: stress test for merges</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#499a1d11</link>
        <description>selftest: sync: stress test for mergesThis test is based on the libsync test suite from Android.This commit includes a test to stress merge operations.Signed-off-by: Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Wed, 19 Oct 2016 12:49:54 +0000</pubDate>
        <dc:creator>Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>c52dee50 - selftest: sync: stress consumer/producer test</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#c52dee50</link>
        <description>selftest: sync: stress consumer/producer testThis test is based on the libsync test suite from Android.This commit includes a stress test that replicates aconsumer/producer pattern.Signed-off-by: Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Wed, 19 Oct 2016 12:49:53 +0000</pubDate>
        <dc:creator>Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>54b519f3 - selftest: sync: stress test for parallelism</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#54b519f3</link>
        <description>selftest: sync: stress test for parallelismThis test is based on the libsync test suite from Android.This commit includes a stress test that invokes operationsin parallel.Signed-off-by: Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Wed, 19 Oct 2016 12:49:52 +0000</pubDate>
        <dc:creator>Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>fdba7cff - selftest: sync: wait tests for sw_sync framework</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#fdba7cff</link>
        <description>selftest: sync: wait tests for sw_sync frameworkThese tests are based on the libsync test suite from Android.This commit includes tests for waiting on fences.Signed-off-by: Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Wed, 19 Oct 2016 12:49:51 +0000</pubDate>
        <dc:creator>Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>1c5839c6 - selftest: sync: merge tests for sw_sync framework</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#1c5839c6</link>
        <description>selftest: sync: merge tests for sw_sync frameworkThese tests are based on the libsync test suite from Android.This commit includes tests for basic merge operations.Signed-off-by: Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Wed, 19 Oct 2016 12:49:50 +0000</pubDate>
        <dc:creator>Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>6a5b7d2c - selftest: sync: fence tests for sw_sync framework</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#6a5b7d2c</link>
        <description>selftest: sync: fence tests for sw_sync frameworkThese tests are based on the libsync test suite from Android.This commit includes tests for basic fence creation.Signed-off-by: Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Wed, 19 Oct 2016 12:49:49 +0000</pubDate>
        <dc:creator>Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>82208160 - selftest: sync: basic tests for sw_sync framework</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/sync/Makefile#82208160</link>
        <description>selftest: sync: basic tests for sw_sync frameworkThese tests are based on the libsync test suite from Android.This commit lays the ground for future tests, as well as includestests for a variety of basic allocation commands.Signed-off-by: Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/sync/Makefile</description>
        <pubDate>Wed, 19 Oct 2016 12:49:48 +0000</pubDate>
        <dc:creator>Emilio L&#243;pez &lt;emilio.lopez@collabora.co.uk&gt;</dc:creator>
    </item>
</channel>
</rss>
