kbuild: remove PYTHON variablePython retired in 2020, and some distributions do not provide the'python' command any more.As in commit 51839e29cb59 ("scripts: switch explicitly to Python 3"),we
kbuild: remove PYTHON variablePython retired in 2020, and some distributions do not provide the'python' command any more.As in commit 51839e29cb59 ("scripts: switch explicitly to Python 3"),we need to use more specific 'python3' to invoke scripts even if theyare written in a way compatible with both Python 2 and 3.This commit removes the variable 'PYTHON', and switches the existingusers to 'PYTHON3'.BTW, PEP 394 (https://www.python.org/dev/peps/pep-0394/) is a helpfulmaterial.Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
show more ...
tweewide: Fix most Shebang linesChange every shebang which does not need an argument to use /usr/bin/env.This is needed as not every distro has everything under /usr/bin,sometimes not even bash.
tweewide: Fix most Shebang linesChange every shebang which does not need an argument to use /usr/bin/env.This is needed as not every distro has everything under /usr/bin,sometimes not even bash.Signed-off-by: Finn Behrens <me@kloenk.de>Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
ia64: convert unwcheck.py to python3Since my system use python3 as default, arch/ia64/scripts/unwcheck.py nolonger run.This patch convert it to the python3 syntax.I have ran it with python2/pyt
ia64: convert unwcheck.py to python3Since my system use python3 as default, arch/ia64/scripts/unwcheck.py nolonger run.This patch convert it to the python3 syntax.I have ran it with python2/python3 while printing values ofstart/end/rlen_sum which could be impacted by this change and I see no difference.Fixes: 94a47083522e ("scripts: change scripts to use system python instead of env")Signed-off-by: Corentin Labbe <clabbe@baylibre.com>Signed-off-by: Tony Luck <tony.luck@intel.com>
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
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 <kstewart@linuxfoundation.org>Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>Reviewed-by: Thomas Gleixner <tglx@linutronix.de>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
ia64: remove paravirt codeAll the ia64 pvops code is now dead code since bothxen and kvm support have been ripped out [0] [1]. Justthat no one had troubled to rip this stuff out. The onlyuseful
ia64: remove paravirt codeAll the ia64 pvops code is now dead code since bothxen and kvm support have been ripped out [0] [1]. Justthat no one had troubled to rip this stuff out. The onlyuseful remaining pieces were the old pvops docs but thatwas recently also generalized and moved out from ia64 [2].This has been run time tested on an ia64 Madison system.[0] 003f7de625890 "KVM: ia64: remove" since v3.19-rc1[1] d52eefb47d4eb "ia64/xen: Remove Xen support for ia64" since v3.14-rc1[2] "virtual: Documentation: simplify and generalize paravirt_ops.txt"Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>Signed-off-by: Tony Luck <tony.luck@intel.com>
scripts: change scripts to use system python instead of envJust a small change to a couple of scripts to go from #!/usr/bin/env pythonto #!/usr/bin/pythonThis shouldn't effect anyone, unles
scripts: change scripts to use system python instead of envJust a small change to a couple of scripts to go from #!/usr/bin/env pythonto #!/usr/bin/pythonThis shouldn't effect anyone, unless they don't install python there.In preparation for python3, Fedora is doing a big push to change the scriptsto use the system python. This allows developers to put the python3 intheir path without fear of breaking existing scripts.Now I am pretty sure anyone using python3 for testing purposes will probablynot run any of the scripts I changed, but Fedora has this automated toolthat checks for this stuff so I thought I would try to push it upstream.Signed-off-by: Don Zickus <dzickus@redhat.com>Acked-by: WANG Cong <xiyou.wangcong@gmail.com>Acked-by: Jarod Wilson <jarod@redhat.com>Signed-off-by: Michal Marek <mmarek@suse.cz>
ia64/pv_ops/pvchecker: support mov = ar.itc paravirtualizationadd suport for mov = ar.itc to pvchecker.Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>Signed-off-by: Tony Luck <tony.luck@i
ia64/pv_ops/pvchecker: support mov = ar.itc paravirtualizationadd suport for mov = ar.itc to pvchecker.Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>Signed-off-by: Tony Luck <tony.luck@intel.com>
ia64/pv_ops: paravirtualized instruction checker.This patch implements a checker to detect instructions whichshould be paravirtualized instead of direct writing raw instruction.This patch does ro
ia64/pv_ops: paravirtualized instruction checker.This patch implements a checker to detect instructions whichshould be paravirtualized instead of direct writing raw instruction.This patch does rough check so that it doesn't fully cover all cases,but it can detects most cases of paravirtualization breakage of handwritten assembly codes.Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>Signed-off-by: Tony Luck <tony.luck@intel.com>
[IA64] don't assume that unwcheck.py is executableDon't assume that this file has execute permissions. For example, patch(1)loses that information.Signed-off-by: Andrew Morton <akpm@linux-found
[IA64] don't assume that unwcheck.py is executableDon't assume that this file has execute permissions. For example, patch(1)loses that information.Signed-off-by: Andrew Morton <akpm@linux-foundation.org>Signed-off-by: Tony Luck <tony.luck@intel.com>
[IA64] check-segrel.lds vs --build-idSome versions of ld with --build-id support will crash when using the flagwith a linker script that discards notes. This bites ia64's check-segrel.lds.The bu
[IA64] check-segrel.lds vs --build-idSome versions of ld with --build-id support will crash when using the flagwith a linker script that discards notes. This bites ia64's check-segrel.lds.The bug is easy to avoid.Signed-off-by: Roland McGrath <roland@redhat.com>Signed-off-by: Tony Luck <tony.luck@intel.com>
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
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!