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/fs/jffs2/Makefile

c799aca3 - [JFFS2] Add LZO compression support.

Tue, 10 Jul 2007 09:28:36 +0000

[JFFS2] Add LZO compression support.Add LZO1X compression/decompression support to jffs2.LZO's interface doesn't entirely match that required by jffs2 so abuffer and memcpy is unavoidable.Signed-off-by: Richard Purdie Signed-off-by: David Woodhouse List of files: /linux-6.15/fs/jffs2/Makefile

c00c310e - [JFFS2] Tidy up licensing/copyright boilerplate.

Wed, 25 Apr 2007 13:16:47 +0000

[JFFS2] Tidy up licensing/copyright boilerplate.In particular, remove the bit in the LICENCE file about contactingRed Hat for alternative arrangements. Their errant IS department brokethat arrangement a long time ago -- the policy of collecting copyrightassignments from contributors came to an end when the plug was pulled onthe servers hosting the project, without notice or reason.We do still dual-license it for use with eCos, with the GPL+exceptionlicence approved by the FSF as being GPL-compatible. It's just that nobodyhas the right to license it differently.Signed-off-by: David Woodhouse List of files: /linux-6.15/fs/jffs2/Makefile

aa98d7cf - [JFFS2][XATTR] XATTR support on JFFS2 (version. 5)

Sat, 13 May 2006 06:09:47 +0000

[JFFS2][XATTR] XATTR support on JFFS2 (version. 5)This attached patches provide xattr support including POSIX-ACL andSELinux support on JFFS2 (version.5).There are some significant differences from previous version postedat last December.The biggest change is addition of EBS(Erase Block Summary) support.Currently, both kernel and usermode utility (sumtool) can recognizexattr nodes which have JFFS2_NODETYPE_XATTR/_XREF nodetype.In addition, some bugs are fixed.- A potential race condition was fixed.- Unexpected fail when updating a xattr by same name/value pair was fixed.- A bug when removing xattr name/value pair was fixed.The fundamental structures (such as using two new nodetypes and exclusionmechanism by rwsem) are unchanged. But most of implementation were reviewedand updated if necessary.Espacially, we had to change several internal implementations related toload_xattr_datum() to avoid a potential race condition.[1/2] xattr_on_jffs2.kernel.version-5.patch[2/2] xattr_on_jffs2.utils.version-5.patchSigned-off-by: KaiGai Kohei Signed-off-by: David Woodhouse List of files: /linux-6.15/fs/jffs2/Makefile

e631ddba - [JFFS2] Add erase block summary support (mount time improvement)

Wed, 07 Sep 2005 08:35:26 +0000

[JFFS2] Add erase block summary support (mount time improvement)The goal of summary is to speed up the mount time. Erase block summary (EBS)stores summary information at the end of every (closed) erase block. It isno longer necessary to scan all nodes separetly (and read all pages of them)just read this "small" summary, where every information is stored which isneeded at mount time.This summary information is stored in a JFFS2_FEATURE_RWCOMPAT_DELETE. Duringthe mount process if there is no summary info the orignal scan process willbe executed. EBS works with NAND and NOR flashes, too.There is a user space tool called sumtool to generate this summaryinformation for a JFFS2 image.Signed-off-by: Ferenc Havasi Signed-off-by: Thomas Gleixner List of files: /linux-6.15/fs/jffs2/Makefile

730554d9 - [JFFS2] Debug code clean up - step 1

Sun, 17 Jul 2005 06:56:26 +0000

[JFFS2] Debug code clean up - step 1Move debug functions into a seperate source fileSigned-off-by: Artem B. Bityutskiy Signed-off-by: Thomas Gleixner List of files: /linux-6.15/fs/jffs2/Makefile

2f82ce1e - [JFFS2] Use a single config option for write buffer support

Wed, 09 Feb 2005 09:24:26 +0000

[JFFS2] Use a single config option for write buffer supportThis patch replaces the current CONFIG_JFFS2_FS_NAND, CONFIG_JFFS2_FS_NOR_ECCand CONFIG_JFFS2_FS_DATAFLASH with a single configuration option -CONFIG_JFFS2_FS_WRITEBUFFER.The only functional change of this patch is that the slower div/modcalculations for SECTOR_ADDR(), PAGE_DIV() and PAGE_MOD() are now alwaysused when CONFIG_JFFS2_FS_WRITEBUFFER is enabled.Signed-off-by: Andrew Victor Signed-off-by: Thomas Gleixner List of files: /linux-6.15/fs/jffs2/Makefile

8f15fd55 - [JFFS2] Add support for JFFS2-on-Dataflash devices.

Wed, 09 Feb 2005 09:17:45 +0000

[JFFS2] Add support for JFFS2-on-Dataflash devices.For Dataflash, can_mark_obsolete = false and the NAND write bufferingcode (wbuf.c) is used.Since the DataFlash chip will automatically erase pages when writing,the cleanmarkers are not needed - so cleanmarker_oob = false andcleanmarker_size = 0DataFlash page-sizes are not a power of two (they're multiples of 528bytes). The SECTOR_ADDR macro (added in the previous core patch) isreplaced with a (slower) div/mod version if CONFIG_JFFS2_FS_DATAFLASH isselected.Signed-off-by: Andrew Victor Signed-off-by: Thomas Gleixner List of files: /linux-6.15/fs/jffs2/Makefile

1da177e4 - Linux-2.6.12-rc2

Sat, 16 Apr 2005 22:20:36 +0000

Linux-2.6.12-rc2Initial git repository build. I'm not bothering with the full history,even though we have it. We can create a separate "historical" gitarchive of that later if we want to, and in the meantime it's about3.2GB when imported into git - space that would just make the earlygit days unnecessarily complicated, when we don't have a lot of goodinfrastructure for it.Let it rip! List of files: /linux-6.15/fs/jffs2/Makefile