Changes in 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/zram/Makefile

80d443e8 - selftests: add EXTRA_CLEAN for clean target

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

selftests: add EXTRA_CLEAN for clean targetSome testcases need the clean extra data after running. This patchintroduce the "EXTRA_CLEAN" 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 Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/zram/Makefile

7eba7d90 - selftests/zram: Makefile fix

Mon, 31 Aug 2015 11:41:56 +0000

selftests/zram: Makefile fixDo not override run_tests, The default rule will just run TEST_PROGSSigned-off-by: Naresh Kamboju Acked-by: Michael Ellerman Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/zram/Makefile

f21fb798 - selftests/zram: Adding zram tests

Tue, 18 Aug 2015 07:01:59 +0000

selftests/zram: Adding zram testszram: Compressed RAM based block devices----------------------------------------The zram module creates RAM based block devices named /dev/zram( = 0, 1, ...). Pages written to these disks are compressed and storedin memory itself. These disks allow very fast I/O and compression providesgood amounts of memory savings. Some of the usecases include /tmp storage,use as swap disks, various caches under /var and maybe many more :)Statistics for individual zram devices are exported through sysfs nodes at/sys/block/zram/This patch is to validate the zram functionality. Test interacts with blockdevice /dev/zram and sysfs nodes /sys/block/zram/zram.sh: sanity check of CONFIG_ZRAM and to run zram01 and zram02 testszram01.sh: creates general purpose ram disks with different filesystemszram02.sh: creates block device for swapzram_lib.sh: create library with initialization/cleanup functionsREADME: ZRAM introduction and Kconfig required.Makefile: To run zram testszram test output-----------------./zram.sh--------------------running zram tests--------------------/dev/zram0 device file found: OKset max_comp_streams to zram device(s)/sys/block/zram0/max_comp_streams = '2' (1/1)zram max streams: OKtest that we can set compression algorithmsupported algs: [lzo] lz4/sys/block/zram0/comp_algorithm = 'lzo' (1/1)zram set compression algorithm: OKset disk size to zram device(s)/sys/block/zram0/disksize = '2097152' (1/1)zram set disksizes: OKset memory limit to zram device(s)/sys/block/zram0/mem_limit = '2M' (1/1)zram set memory limit: OKmake ext4 filesystem on /dev/zram0zram mkfs.ext4: OKmount /dev/zram0zram mount of zram device(s): OKfill zram0...zram0 can be filled with '1932' KBzram used 3M, zram disk sizes 2097152Mzram compression ratio: 699050.66:1: OKzram cleanupzram01 : [PASS]/dev/zram0 device file found: OKset max_comp_streams to zram device(s)/sys/block/zram0/max_comp_streams = '2' (1/1)zram max streams: OKset disk size to zram device(s)/sys/block/zram0/disksize = '1048576' (1/1)zram set disksizes: OKset memory limit to zram device(s)/sys/block/zram0/mem_limit = '1M' (1/1)zram set memory limit: OKmake swap with zram device(s)done with /dev/zram0zram making zram mkswap and swapon: OKzram swapoff: OKzram cleanupzram02 : [PASS]CC: Shuah Khan CC: Tyler Baker CC: Milosz Wasilewski CC: Alexey Kodanev Signed-off-by: Naresh Kamboju Signed-off-by: Alexey Kodanev Reviewed-By: Tyler Baker Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/zram/Makefile