<?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>80c3e285 - selftests/tracing: Add hist poll() support test</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#80c3e285</link>
        <description>selftests/tracing: Add hist poll() support testAdd a testcase for poll() on hist file. This introduces a helper binaryto the ftracetest, because there is no good way to reliably executepoll() on hist file.Cc: Shuah Khan &lt;shuah@kernel.org&gt;Cc: Tom Zanussi &lt;zanussi@kernel.org&gt;Cc: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;Link: https://lore.kernel.org/173547867935.569911.10127126796879854182.stgit@devnote2Signed-off-by: Masami Hiramatsu (Google) &lt;mhiramat@kernel.org&gt;Reviewed-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;Signed-off-by: Steven Rostedt (Google) &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/ftrace/Makefile</description>
        <pubDate>Sun, 29 Dec 2024 13:24:39 +0000</pubDate>
        <dc:creator>Masami Hiramatsu (Google) &lt;mhiramat@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>dbcf7639 - selftests/ftrace: Improve integration with kselftest runner</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#dbcf7639</link>
        <description>selftests/ftrace: Improve integration with kselftest runnerThe ftrace selftests do not currently produce KTAP output, they produce acustom format much nicer for human consumption. This means that when run inautomated test systems we just get a single result for the suite as a wholerather than recording results for individual test cases, making it harderto look at the test data and masking things like inappropriate skips.Address this by adding support for KTAP output to the ftracetest script andproviding a trivial wrapper which will be invoked by the kselftest runnerto generate output in this format by default, users using ftracetestdirectly will continue to get the existing output.This is not the most elegant solution but it is simple and effective. Idid consider implementing this by post processing the existing outputformat but that felt more complex and likely to result in all output beinglost if something goes seriously wrong during the run which would not behelpful. I did also consider just writing a separate runner script butthere&apos;s enough going on with things like the signal handling for that toseem like it would be duplicating too much.Acked-by: Steven Rostedt (Google) &lt;rostedt@goodmis.org&gt;Acked-by: Masami Hiramatsu (Google) &lt;mhiramat@kernel.org&gt;Tested-by: Masami Hiramatsu (Google) &lt;mhiramat@kernel.org&gt;Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/ftrace/Makefile</description>
        <pubDate>Mon, 08 May 2023 13:15:42 +0000</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b9167c80 - selftests: Install settings files to fix TIMEOUT failures</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#b9167c80</link>
        <description>selftests: Install settings files to fix TIMEOUT failuresCommit 852c8cbf34d3 (&quot;selftests/kselftest/runner.sh: Add 45 secondtimeout per test&quot;) added a 45 second timeout for tests, and also addeda way for tests to customise the timeout via a settings file.For example the ftrace tests take multiple minutes to run, so theywere given longer in commit b43e78f65b1d (&quot;tracing/selftests: Turn offtimeout setting&quot;).This works when the tests are run from the source tree. However if thetests are installed with &quot;make -C tools/testing/selftests install&quot;,the settings files are not copied into the install directory. When thetests are then run from the install directory the longer timeouts arenot applied and the tests timeout incorrectly.So add the settings files to TEST_FILES of the appropriate Makefilesto cause the settings files to be installed using the existing installlogic.Fixes: 852c8cbf34d3 (&quot;selftests/kselftest/runner.sh: Add 45 second timeout per test&quot;)Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/ftrace/Makefile</description>
        <pubDate>Thu, 20 Feb 2020 04:42:41 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&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/ftrace/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/ftrace/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>a8ba798b - selftests: enable O and KBUILD_OUTPUT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#a8ba798b</link>
        <description>selftests: enable O and KBUILD_OUTPUTEnable O and KBUILD_OUTPUT for kselftest. User could compile kselftestto another directory by passing O or KBUILD_OUTPUT. And O is highpriority than KBUILD_OUTPUT.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/ftrace/Makefile</description>
        <pubDate>Tue, 29 Nov 2016 11:55:52 +0000</pubDate>
        <dc:creator>bamvor.zhangjian@huawei.com &lt;bamvor.zhangjian@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>80d443e8 - selftests: add EXTRA_CLEAN for clean target</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#80d443e8</link>
        <description>selftests: add EXTRA_CLEAN for clean targetSome testcases need the clean extra data after running. This patchintroduce the &quot;EXTRA_CLEAN&quot; variable to address this requirement.After KBUILD_OUTPUT is enabled in later patch, it will be easy todecide to if we need do the cleanup in the KBUILD_OUTPUT path(if thetestcase ran immediately after compiled).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/ftrace/Makefile</description>
        <pubDate>Tue, 29 Nov 2016 11:55:51 +0000</pubDate>
        <dc:creator>bamvor.zhangjian@huawei.com &lt;bamvor.zhangjian@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>5fe59799 - selftests: remove useless TEST_DIRS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#5fe59799</link>
        <description>selftests: remove useless TEST_DIRSThe TEST_DIRS was introduced in Commit e8c1d7cdf137 (&quot;selftests: copyTEST_DIRS to INSTALL_PATH&quot;) for coping a whole directory in ftrace.After rsync(with -a) is introduced by Commit 900d65ee11aa (&quot;selftests:change install command to rsync&quot;). Rsync could handle the directorywithout the definition of TEST_DIRS.This patch simply replace TEST_DIRS with TEST_FILES in ftrace and removethe TEST_DIRS in tools/testing/selftest/lib.mkAcked-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;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/ftrace/Makefile</description>
        <pubDate>Tue, 29 Nov 2016 11:55:48 +0000</pubDate>
        <dc:creator>bamvor.zhangjian@huawei.com &lt;bamvor.zhangjian@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>900d65ee - selftests: change install command to rsync</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#900d65ee</link>
        <description>selftests: change install command to rsyncThe command of install could not handle the special files in exectestcases, change the default rule to rsync to fix this.The installation is unchanged after this commit.Suggested-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;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/ftrace/Makefile</description>
        <pubDate>Wed, 09 Sep 2015 13:06:28 +0000</pubDate>
        <dc:creator>Bamvor Jian Zhang &lt;bamvor.zhangjian@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>3bc54b5a - selftests/ftrace: install test.d</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#3bc54b5a</link>
        <description>selftests/ftrace: install test.dThe ftrace test requires the directory test.d and all of it&apos;s contents to bepresent during execution. Use TEST_DIRS to ensure this is copied to theINSTALL_PATH.Acked-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Signed-off-by: Tyler Baker &lt;tyler.baker@linaro.org&gt;Signed-off-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/ftrace/Makefile</description>
        <pubDate>Tue, 21 Apr 2015 22:50:01 +0000</pubDate>
        <dc:creator>Tyler Baker &lt;tyler.baker@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/ftrace/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/ftrace/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>6e68e6c5 - ftracetest: Initial commit for ftracetest</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/ftrace/Makefile#6e68e6c5</link>
        <description>ftracetest: Initial commit for ftracetestftracetest is a collection of testcase shell-scripts for ftrace.To avoid regressions of ftrace, these testcases check correctftrace behaviors. If someone would like to add any features onftrace, the patch series should have at least one testcase forchecking the new behavior.Link: http://lkml.kernel.org/p/20140922234250.23415.68758.stgit@kbuild-f20.novalocalAcked-by: Shuah Khan &lt;shuahkh@osg.samsung.com&gt;Acked-by: Namhyung Kim &lt;namhyung@kernel.org&gt;Signed-off-by: Masami Hiramatsu &lt;masami.hiramatsu.pt@hitachi.com&gt;Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/ftrace/Makefile</description>
        <pubDate>Mon, 22 Sep 2014 23:42:50 +0000</pubDate>
        <dc:creator>Masami Hiramatsu &lt;masami.hiramatsu.pt@hitachi.com&gt;</dc:creator>
    </item>
</channel>
</rss>
