Changes in Makefile

32c75ad4 - selftests/futex: don't redefine .PHONY targets (all, clean)

Fri, 31 May 2024 20:07:53 +0000

selftests/futex: don't redefine .PHONY targets (all, clean)The .PHONY targets "all" and "clean" are both already defined in thefile that is included in the very next line: ../lib.mk.Remove this duplicate code.Reviewed-by: Davidlohr Bueso Signed-off-by: John Hubbard Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

b9199181 - selftests: futex: Use variable MAKE instead of make

Thu, 27 Jan 2022 17:44:46 +0000

selftests: futex: Use variable MAKE instead of makeRecursive make commands should always use the variable MAKE, not theexplicit command name ‘make’. This has benefits and removes thefollowing warning when multiple jobs are used for the build:make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")Signed-off-by: Muhammad Usama Anjum Reviewed-by: André Almeida Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

99a5d09b - selftests: futex: delete RUN_TESTS and EMIT_TESTS overrides

Wed, 02 May 2018 01:34:19 +0000

selftests: futex: delete RUN_TESTS and EMIT_TESTS overridesDelete RUN_TESTS and EMIT_TESTS overrides and use common defines inlib.mk. Common defines work just fine and there is no need to definecustom overrides.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/futex/Makefile

78972f51 - selftests: futex Makefile add top level TAP header echo to RUN_TESTS

Fri, 23 Feb 2018 01:17:50 +0000

selftests: futex Makefile add top level TAP header echo to RUN_TESTSAdd top level TAP header echo, testname and separator line to makethe output consistent with the common run_tests target.This change prevents nested TAP13 headers output from individual tests.Nested TAP13 headers could cause problems for some parsers.Signed-off-by: Shuah Khan Reviewed-by: Darren Hart (VMware) Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

067b25a5 - selftests/futex: Fix line continuation in Makefile

Wed, 07 Feb 2018 17:24:31 +0000

selftests/futex: Fix line continuation in MakefileThe Makefile lacks a couple of line continuation backslashesin an `if' clause, which produces an error when make versionsprior to 4.x are used for building the tests. $ make make[1]: Entering directory `/[...]/linux/tools/testing/selftests/futex' /bin/sh: -c: line 5: syntax error: unexpected end of file make[1]: *** [all] Error 1 make[1]: Leaving directory `/[...]/linux/tools/testing/selftests/futex' make: *** [all] Error 2Signed-off-by: Daniel Díaz Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/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/futex/Makefile

659dbfd8 - selftests: futex: Makefile: fix for loops in targets to run silently

Tue, 19 Sep 2017 00:46:23 +0000

selftests: futex: Makefile: fix for loops in targets to run silentlyFix for loops in targets to run silently to avoid cluttering the testresults.Suppresses the following from targets:for DIR in functional; do \ BUILD_TARGET=./tools/testing/selftests/futex/$DIR; \ mkdir $BUILD_TARGET -p; \ make OUTPUT=$BUILD_TARGET -C $DIR all;\done./tools/testing/selftests/futex/run.shSigned-off-by: Shuah Khan Reviewed-by: Darren Hart (VMware) Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

9c3340ea - selftests: futex: copy sub-dir test scripts for make O=dir run

Tue, 12 Sep 2017 01:11:07 +0000

selftests: futex: copy sub-dir test scripts for make O=dir runFor make O=dir run_tests to work, test scripts from sub-directoriesneed to be copied over to the object directory. Running tests from theobject directory is necessary to avoid making the source tree dirty.Signed-off-by: Shuah Khan Reviewed-by: Darren Hart (VMware) Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

7ba190be - selftests: futex: fix run_tests target

Wed, 02 Aug 2017 21:47:33 +0000

selftests: futex: fix run_tests targetmake -C tools/testing/selftests/futex/ run_tests doesn't run the futextests.Running the tests when `dirname $(OUTPUT)` == $(PWD) doesn't work whenthe $(OUTPUT) is $(PWD) which is the case when the test is run usingmake -C tools/testing/selftests/futex/ run_tests.Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")Signed-off-by: Shuah Khan Reviewed-by: Darren Hart (VMware) Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

b1c0f540 - selftests: futex: override clean in lib.mk to fix warnings

Fri, 21 Apr 2017 22:12:22 +0000

selftests: futex: override clean in lib.mk to fix warningsAdd override for lib.mk clean to fix the following warnings from cleantarget run.Makefile:36: warning: overriding recipe for target 'clean'../lib.mk:55: warning: ignoring old recipe for target 'clean'Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

bfedc31c - selftests/futex: Fix build error with OUTPUT variable

Fri, 24 Mar 2017 16:18:54 +0000

selftests/futex: Fix build error with OUTPUT variableThe use of $$OUTPUT in the target shell commands resulted in an emptystring followed by an absolute path for which mkdir failed:$ make -C tools/testing/selftests/futexmake: Entering directory '/home/dvhart/source/linux/linux-pdx86/tools/testing/selftests/futex'Makefile:36: warning: overriding recipe for target 'clean'../lib.mk:55: warning: ignoring old recipe for target 'clean'for DIR in functional; do \ BUILD_TARGET=$OUTPUT/$DIR; \ mkdir $BUILD_TARGET -p; \ make OUTPUT=$BUILD_TARGET -C $DIR all;\donemkdir: cannot create directory ‘/functional’: Permission deniedReplace $$OUTPUT with $(OUTPUT) when referring to the Makefile OUTPUTvariable. The above make command now completes successfully.Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")Signed-off-by: Darren Hart (VMware) Cc: linux-kselftest@vger.kernel.orgCc: bamvor.zhangjian@huawei.comCc: Shuah Khan Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

a8ba798b - selftests: enable O and KBUILD_OUTPUT

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

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

9705315b - selftests/futex: Update Makefile to use lib.mk

Wed, 13 May 2015 04:07:53 +0000

selftests/futex: Update Makefile to use lib.mkAdapt the futextest Makefiles to use lib.mk macros for RUN_TESTS andEMIT_TESTS. For now, we reuse the run.sh mechanism provided byfutextest. This doesn't provide the standard selftests: [PASS|FAIL]format, but the tests provide very similar output already.This results in the run_kselftest.sh script for futexes including asingle line: ./run.shCc: Shuah Khan Cc: linux-api@vger.kernel.orgCc: Ingo Molnar Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: Davidlohr Bueso Cc: KOSAKI Motohiro Signed-off-by: Darren Hart Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile

2aa8470f - selftests: Add futex functional tests

Wed, 13 May 2015 04:07:52 +0000

selftests: Add futex functional testsThe futextest testsuite [1] provides functional, stress, andperformance tests for the various futex op codes. Those tests will be ofmore use to futex developers if they are included with the kernelsource.Copy the core infrastructure and the functional tests into selftests,but adapt them for inclusion in the kernel:- Update the Makefile to include the run_tests target, remove reference to the performance and stress tests from the contributed sources.- Replace my dead IBM email address with my current Intel email address.- Remove the warrantee and write-to paragraphs from the license blurbs.- Remove the NAME section as the filename is easily determined. ;-)- Make the whitespace usage consistent in a couple of places.- Cleanup various CodingStyle violations.A future effort will explore moving the performance and stress testsinto the kernel.1. http://git.kernel.org/cgit/linux/kernel/git/dvhart/futextest.gitCc: Shuah Khan Cc: linux-api@vger.kernel.orgCc: Ingo Molnar Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: Davidlohr Bueso Cc: KOSAKI Motohiro Signed-off-by: Darren Hart Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/futex/Makefile