<?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>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/breakpoints/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/breakpoints/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>172a8ca8 - selftests: breakpoints: re-order TEST_GEN_PROGS targets</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#172a8ca8</link>
        <description>selftests: breakpoints: re-order TEST_GEN_PROGS targetsbreakpoint_test can fail on arm64 with older/unpatched glibc: breakpoint_test_arm64.c: In function &apos;run_test&apos;: breakpoint_test_arm64.c:170:25: error: &apos;TRAP_HWBKPT&apos; undeclared (first use in this function)due to glibc missing several of the TRAP_* constants in the userspacedefinitions. Specifically TRAP_BRANCH and TRAP_HWBKPT.See https://sourceware.org/bugzilla/show_bug.cgi?id=21286It prevents to build step_after_suspend_test afterward, since make won&apos;tcontinue.We still want to be able to build and run the test, independently ofbreakpoint_test_arm64 build failure. Re-order TEST_GEN_PROGS to be able tobuild step_after_suspend_test first.Signed-off-by: Fathi Boudra &lt;fathi.boudra@linaro.org&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Thu, 29 Jun 2017 09:39:53 +0000</pubDate>
        <dc:creator>Fathi Boudra &lt;fathi.boudra@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>b13f7666 - selftests: breakpoints: allow to cross-compile for aarch64/arm64</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#b13f7666</link>
        <description>selftests: breakpoints: allow to cross-compile for aarch64/arm64To build breakpoint_test_arm64, ARCH value is only tested for &quot;aarch64&quot;.It covers only the native build because it&apos;s computed from uname -m output.For cross-compilation, ARCH is set to arm64 and prevent to cross-compilethe test.Fix the test to allow both native and cross-compilation of the test.Note: glibc is missing several of the TRAP_* constants in the userspace      definitions. Specifically TRAP_BRANCH and TRAP_HWBKPT.      See https://sourceware.org/bugzilla/show_bug.cgi?id=21286Signed-off-by: Fathi Boudra &lt;fathi.boudra@linaro.org&gt;Tested-by: Naresh Kamboju &lt;naresh.kamboju@linaro.org&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Wed, 22 Mar 2017 18:04:58 +0000</pubDate>
        <dc:creator>Fathi Boudra &lt;fathi.boudra@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>88baa78d - selftests: remove duplicated all and clean target</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#88baa78d</link>
        <description>selftests: remove duplicated all and clean targetCurrently, kselftest use TEST_PROGS, TEST_PROGS_EXTENDED, TEST_FILES toindicate the test program, extended test program and test files. It iseasy to understand the purpose of these files. But mix of compiled anduncompiled files lead to duplicated &quot;all&quot; and &quot;clean&quot; targets.In order to remove the duplicated targets, introduce TEST_GEN_PROGS,TEST_GEN_PROGS_EXTENDED, TEST_GEN_FILES to indicate the compiledobjects.Also, the later patch will make use of TEST_GEN_XXX to redirect thesefiles to output directory indicated by KBUILD_OUTPUT or O.And add this changes to &quot;Contributing new tests(details)&quot; ofDocumentation/kselftest.txt.Signed-off-by: Bamvor Jian Zhang &lt;bamvor.zhangjian@linaro.org&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Tue, 29 Nov 2016 11:55:47 +0000</pubDate>
        <dc:creator>bamvor.zhangjian@huawei.com &lt;bamvor.zhangjian@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>f43365ee - selftests: arm64: add test for unaligned/inexact watchpoint handling</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#f43365ee</link>
        <description>selftests: arm64: add test for unaligned/inexact watchpoint handlingARM64 hardware expects 64bit aligned address for watchpoint invocation.However, it provides byte selection method to select any number ofconsecutive byte set within the range of 1-8.This patch adds support to test all such byte selection option fordifferent memory write sizes.Patch also adds a test for handling the case when the cpu does notreport an address which exactly matches one of the regions we havebeen watching (which is a situation permitted by the spec if aninstruction accesses both watched and unwatched regions). The testwas failing on a MSM8996pro before this patch series and ispassing now.Signed-off-by: Pavel Labath &lt;labath@google.com&gt;Signed-off-by: Pratyush Anand &lt;panand@redhat.com&gt;Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Mon, 14 Nov 2016 14:02:46 +0000</pubDate>
        <dc:creator>Pratyush Anand &lt;panand@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>bfd092b8 - selftests: breakpoint: add step_after_suspend_test</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#bfd092b8</link>
        <description>selftests: breakpoint: add step_after_suspend_testCommit e56d82a11617 (&quot;arm64: cpu hotplug: ensure we mask outCPU_TASKS_FROZEN in notifiers&quot;) fixed a long-standing ARM64 bug thatbroke single-stepping after a suspend/resume cycle.  Add a kernelselftest to make sure this doesn&apos;t regress or affect other platforms.Signed-off-by: Greg Hackmann &lt;ghackmann@google.com&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Mon, 22 Feb 2016 18:10:57 +0000</pubDate>
        <dc:creator>Greg Hackmann &lt;ghackmann@google.com&gt;</dc:creator>
    </item>
<item>
        <title>3b5bab39 - selftests: breakpoint: Actually build it</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#3b5bab39</link>
        <description>selftests: breakpoint: Actually build itFixes: 9fae100cbd10 (&quot;selftests: breakpoints: fix installing error on ...&quot;)Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Mon, 02 Nov 2015 12:22:29 +0000</pubDate>
        <dc:creator>Ben Hutchings &lt;ben@decadent.org.uk&gt;</dc:creator>
    </item>
<item>
        <title>9fae100c - selftests: breakpoints: fix installing error on the architecture except x86</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#9fae100c</link>
        <description>selftests: breakpoints: fix installing error on the architecture except x86Signed-off-by: Bamvor Jian Zhang &lt;bamvor.zhangjian@linaro.org&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Fri, 14 Aug 2015 13:43:38 +0000</pubDate>
        <dc:creator>Bamvor Jian Zhang &lt;bamvor.zhangjian@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>5e29a910 - selftests: Introduce minimal shared logic for running tests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#5e29a910</link>
        <description>selftests: Introduce minimal shared logic for running testsThis adds a Make include file which most selftests can then include toget the run_tests logic.On its own this has the advantage of some reduction in repetition, andalso means the pass/fail message is defined in fewer places.However the key advantage is it will allow us to implement install verysimply in a subsequent patch.The default implementation just executes each program in $(TEST_PROGS).We use a variable to hold the default implementation of $(RUN_TESTS)because that gives us a clean way to override it if necessary, ie. usingoverride. The mount, memory-hotplug and mqueue tests use that to providea different implementation.Tests are not run via /bin/bash, so if they are scripts they must beexecutable, we add a+x to several.Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Wed, 11 Mar 2015 04:05:59 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>5a55f8bb - breakpoint selftests: print failure status instead of cause make error</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#5a55f8bb</link>
        <description>breakpoint selftests: print failure status instead of cause make errorIn case breakpoint test exit non zero value it will cause make error.Better way is just print the test failure status.Signed-off-by: Dave Young &lt;dyoung@redhat.com&gt;Reviewed-by: Pekka Enberg &lt;penberg@kernel.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Tue, 18 Dec 2012 00:04:50 +0000</pubDate>
        <dc:creator>Dave Young &lt;dyoung@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>f467f714 - selftests: launch individual selftests from the main Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#f467f714</link>
        <description>selftests: launch individual selftests from the main MakefileRemove the run_tests script and launch the selftests by calling &quot;makerun_tests&quot; from the selftests top directory instead.  This delegates tothe Makefile in each selftest directory, where it is decided how to launchthe local test.This removes the need to add each selftest directory to the now removed&quot;run_tests&quot; top script.Signed-off-by: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;Cc: Dave Young &lt;dyoung@redhat.com&gt;Cc: Christoph Lameter &lt;cl@linux.com&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Wed, 28 Mar 2012 21:42:54 +0000</pubDate>
        <dc:creator>Frederic Weisbecker &lt;fweisbec@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>85bbddc3 - selftests: new x86 breakpoints selftest</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/breakpoints/Makefile#85bbddc3</link>
        <description>selftests: new x86 breakpoints selftestBring a first selftest in the relevant directory.  This tests severalcombinations of breakpoints and watchpoints in x86, as well as icebp trapsand int3 traps.  Given the amount of breakpoint regressions we raisedafter we merged the generic breakpoint infrastructure, such selftestbecame necessary and can still serve today as a basis for new patches thattouch the do_debug() path.Signed-off-by: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Cc: Ingo Molnar &lt;mingo@elte.hu&gt;Cc: H. Peter Anvin &lt;hpa@zytor.com&gt;Cc: Jason Wessel &lt;jason.wessel@windriver.com&gt;Cc: Will Deacon &lt;will.deacon@arm.com&gt;Cc: Michal Marek &lt;mmarek@suse.cz&gt;Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/breakpoints/Makefile</description>
        <pubDate>Fri, 13 Jan 2012 01:20:46 +0000</pubDate>
        <dc:creator>Frederic Weisbecker &lt;fweisbec@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
