Changes in Makefile

978e9aa1 - selftests: mqueue: delete RUN_TESTS and EMIT_TESTS overrides

Wed, 02 May 2018 19:13:11 +0000

selftests: mqueue: delete RUN_TESTS and EMIT_TESTS overridesDelete RUN_TESTS and EMIT_TESTS overrides and use common defines in lib.mk.The overrides are in place to call mq_open_tests with queue name argument.The change to delete overrides is coupled with a change to mq_open_teststo use default queue name when it is called without one.Signed-off-by: Shuah Khan (Samsung OSG) Reviewed-by: Anders Roxell Signed-off-by: Shuah Khan (Samsung OSG) List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

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 'GPL-2.0'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 & 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 >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn'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 "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". 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'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 Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

ea344f6a - selftests: mqueue: fix regression in silencing output from RUN_TESTS

Mon, 02 Oct 2017 23:02:22 +0000

selftests: mqueue: fix regression in silencing output from RUN_TESTSFix fix regression in silencing output from RUN_TESTS introduced bycommit <8230b905a6780c6> selftests: mqueue: Use full path to run testsfrom MakefileSigned-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

8230b905 - selftests: mqueue: Use full path to run tests from Makefile

Tue, 12 Sep 2017 14:52:13 +0000

selftests: mqueue: Use full path to run tests from MakefileUse full path including $(OUTPUT) to run tests from Makefile fornormal case when objects reside in the source tree as well as whenobjects are relocated with make O=dir. In both cases $(OUTPUT) willbe set correctly by lib.mk.Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

88baa78d - selftests: remove duplicated all and clean target

Tue, 29 Nov 2016 11:55:47 +0000

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 "all" and "clean" 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 "Contributing new tests(details)" ofDocumentation/kselftest.txt.Signed-off-by: Bamvor Jian Zhang Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

b11054b9 - selftests: mqueue: simplify the Makefile

Wed, 09 Sep 2015 13:06:27 +0000

selftests: mqueue: simplify the MakefileUse make's implict rule for building simple C programs.Suggested-by: Michael Ellerman Signed-off-by: Bamvor Jian Zhang Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

cc19ada7 - selftests: mqueue: allow extra cflags

Wed, 09 Sep 2015 13:06:26 +0000

selftests: mqueue: allow extra cflagsChange from = to += in order to allows the user to pass whateverCFLAGS they wish(E.g. pass the proper headers and librareis(popt.h and libpopt.so) in cross-compiling)Suggested-by: Michael Ellerman Signed-off-by: Bamvor Jian Zhang Acked-by: Michael Ellerman Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

6886f41d - selftest/mqueue: enable cross compilation

Wed, 01 Apr 2015 23:20:20 +0000

selftest/mqueue: enable cross compilationUse the CC variable instead of hard coding gcc. Also clean up the compileroptions by creating a CFLAGS variable.Signed-off-by: Tyler Baker Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

32dcfba6 - selftests: Add install target

Wed, 11 Mar 2015 04:06:00 +0000

selftests: Add install targetThis adds make install support to selftests. The basic usage is:$ cd tools/testing/selftests$ make installThat installs into tools/testing/selftests/install, which can then becopied where ever necessary.The install destination is also configurable using eg:$ INSTALL_PATH=/mnt/selftests make installThe implementation uses two targets in the child makefiles. The first"install" is expected to install all files into $(INSTALL_PATH).The second, "emit_tests", is expected to emit the test instructions (ie.bash script) on stdout. Separating this from install means the childmakefiles need no knowledge of the location of the test script.Signed-off-by: Michael Ellerman Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

5e29a910 - selftests: Introduce minimal shared logic for running tests

Wed, 11 Mar 2015 04:05:59 +0000

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 Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

b80f5570 - tools: Fix mqueue Makefile compile linking order

Wed, 25 Jun 2014 01:53:36 +0000

tools: Fix mqueue Makefile compile linking orderMakefile compile linking order is incorrect causing the compileto fail not finding librt symbols./tmp/cceTqwFh.o: In function `test_queue_fail':mq_open_tests.c:(.text+0x6b): undefined reference to `mq_open'mq_open_tests.c:(.text+0x80): undefined reference to `mq_getattr'mq_open_tests.c:(.text+0xa2): undefined reference to `mq_close'mq_open_tests.c:(.text+0xcf): undefined reference to `mq_unlink'/tmp/cceTqwFh.o: In function `test_queue.constprop.6':mq_open_tests.c:(.text+0x15a): undefined reference to `mq_open'mq_open_tests.c:(.text+0x16f): undefined reference to `mq_getattr'mq_open_tests.c:(.text+0x195): undefined reference to `mq_close'mq_open_tests.c:(.text+0x1c2): undefined reference to `mq_unlink'/tmp/cceTqwFh.o: In function `shutdown.part.0':mq_open_tests.c:(.text.unlikely+0x5b): undefined reference to `mq_close'mq_open_tests.c:(.text.unlikely+0x7a): undefined reference to `mq_unlink'collect2: error: ld returned 1 exit statusmake: *** [all] Error 1Signed-off-by: Shuah Khan Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

9ed1d90e - mqueue selftests: print failure status instead of cause make error

Tue, 18 Dec 2012 00:04:39 +0000

mqueue selftests: print failure status instead of cause make errorOriginal behavior: bash-4.1$ make -C mqueue run_tests make: Entering directory `/home/dave/git/linux-2.6/tools/testing/selftests/mqueue' ./mq_open_tests /test1 Not running as root, but almost all tests require root in order to modify system settings. Exiting. make: *** [run_tests] Error 1 make: Leaving directory `/home/dave/git/linux-2.6/tools/testing/selftests/mqueue'After applying the patch: bash-4.1$ make -C mqueue run_tests make: Entering directory `/home/dave/git/linux-2.6/tools/testing/selftests/mqueue' Not running as root, but almost all tests require root in order to modify system settings. Exiting. mq_open_tests: [FAIL] Not running as root, but almost all tests require root in order to modify system settings. Exiting. mq_perf_tests: [FAIL] make: Leaving directory `/home/dave/git/linux-2.6/tools/testing/selftests/mqueue'Signed-off-by: Dave Young Reviewed-by: Pekka Enberg Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

7820b071 - tools/selftests: add mq_perf_tests

Thu, 31 May 2012 23:26:37 +0000

tools/selftests: add mq_perf_testsAdd the mq_perf_tests tool I used when creating my mq performance patch.Also add a local .gitignore to keep the binaries from showing up in gitstatus output.[akpm@linux-foundation.org: checkpatch fixes]Signed-off-by: Doug Ledford Cc: Stephen Rothwell Cc: Manfred Spraul Cc: Frederic Weisbecker Acked-by: KOSAKI Motohiro Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile

50069a58 - selftests: add mq_open_tests

Thu, 31 May 2012 23:26:34 +0000

selftests: add mq_open_testsAdd a directory to house POSIX message queue subsystem specific tests.Add first test which checks the operation of mq_open() under variouscorner conditions.Signed-off-by: Doug Ledford Cc: KOSAKI Motohiro Cc: Doug Ledford Cc: Joe Korty Cc: Amerigo Wang Cc: Serge E. Hallyn Cc: Jiri Slaby Cc: Manfred Spraul Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/testing/selftests/mqueue/Makefile