Changes in Makefile

e2028c8e - lib/fonts: add font 6x8 for OLED display

Thu, 20 Aug 2020 08:21:37 +0000

lib/fonts: add font 6x8 for OLED displayThis font is derived from lib/fonts/font_6x10.c and is useful for smallOLED displaysSigned-off-by: Sven Schneider Signed-off-by: Sascha Hauer Reviewed-by: Greg Kroah-Hartman Signed-off-by: Bartlomiej Zolnierkiewicz Link: https://patchwork.freedesktop.org/patch/msgid/20200820082137.5907-1-s.hauer@pengutronix.de List of files: /linux-6.15/lib/fonts/Makefile

b16838c6 - kbuild: trace functions in subdirectories of lib/

Tue, 07 Jul 2020 09:21:17 +0000

kbuild: trace functions in subdirectories of lib/ccflags-remove-$(CONFIG_FUNCTION_TRACER) += $(CC_FLAGS_FTRACE)exists here in sub-directories of lib/ to keep the behavior ofcommit 2464a609ded0 ("ftrace: do not trace library functions").Since that commit, not only the objects in lib/ but also the ones inthe sub-directories are excluded from ftrace (although the commitdescription did not explicitly mention this).However, most of library functions in sub-directories are not so hot.Re-add them to ftrace.Going forward, only the objects right under lib/ will be excluded.Cc: Ingo Molnar Signed-off-by: Masahiro Yamada Acked-by: Steven Rostedt (VMware) List of files: /linux-6.15/lib/fonts/Makefile

15d5761a - kbuild: introduce ccflags-remove-y and asflags-remove-y

Tue, 07 Jul 2020 09:21:16 +0000

kbuild: introduce ccflags-remove-y and asflags-remove-yCFLAGS_REMOVE_.o filters out flags when compiling a particularobject, but there is no convenient way to do that for every object ina directory.Add ccflags-remove-y and asflags-remove-y to make it easily.Use ccflags-remove-y to clean up some Makefiles.The add/remove order works as follows: [1] KBUILD_CFLAGS specifies compiler flags used globally [2] ccflags-y adds compiler flags for all objects in the current Makefile [3] ccflags-remove-y removes compiler flags for all objects in the current Makefile (New feature) [4] CFLAGS_ adds compiler flags per file. [5] CFLAGS_REMOVE_ removes compiler flags per file.Having [3] before [4] allows us to remove flags from most (but not all)objects in the current Makefile.For example, kernel/trace/Makefile removes $(CC_FLAGS_FTRACE)from all objects in the directory, then adds it back totrace_selftest_dynamic.o and CFLAGS_trace_kprobe_selftest.oThe same applies to lib/livepatch/Makefile.Please note ccflags-remove-y has no effect to the sub-directories.In contrast, the previous notation got rid of compiler flags also fromall the sub-directories.The following are not affected because they have no sub-directories: arch/arm/boot/compressed/ arch/powerpc/xmon/ arch/sh/ kernel/trace/However, lib/ has several sub-directories.To keep the behavior, I added ccflags-remove-y to all Makefilesin subdirectories of lib/, except the following: lib/vdso/Makefile - Kbuild does not descend into this Makefile lib/raid/test/Makefile - This is not used for the kernel buildI think commit 2464a609ded0 ("ftrace: do not trace library functions")excluded too much. In the next commit, I will remove ccflags-remove-yfrom the sub-directories of lib/.Suggested-by: Sami Tolvanen Signed-off-by: Masahiro Yamada Acked-by: Steven Rostedt (VMware) Acked-by: Michael Ellerman (powerpc)Acked-by: Brendan Higgins (KUnit)Tested-by: Anders Roxell List of files: /linux-6.15/lib/fonts/Makefile

ac8b6f14 - Fonts: New Terminus large console font

Wed, 05 Dec 2018 23:56:37 +0000

Fonts: New Terminus large console fontThis patch adds an option to compile-in a high resolutionand large Terminus (ter16x32) bitmap console font for use withHiDPI and Retina screens.The font was convereted from standard Terminus ter-i32b.psf(size 16x32) with the help of psftools and minor hand editingdeleting useless characters.This patch is non-intrusive, no options are enabled by default so mostusers won't notice a thing.I am placing my changes under the GPL 2.0 just as source Terminus font.Signed-off-by: Amanoel Dawod Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/lib/fonts/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/lib/fonts/Makefile

33ac9dba - fonts: Add 6x10 font

Tue, 09 Sep 2014 11:46:28 +0000

fonts: Add 6x10 fontThis font is suitable for framebuffer consoles on devices with a320x240 screen, to get a reasonable number of characters (53x24) thatare still at a readable size.The font is derived from the existing 6x11 font, but gets 3 extralines without sacrificing readability. Also I redesigned a some glyhpsso they are more distinct and better fill the available space.Signed-off-by: Maarten ter Huurne Signed-off-by: Tomi Valkeinen List of files: /linux-6.15/lib/fonts/Makefile

ee89bd6b - lib: Move fonts from drivers/video/console/ to lib/fonts/

Sun, 09 Jun 2013 09:46:43 +0000

lib: Move fonts from drivers/video/console/ to lib/fonts/Several drivers need font support independent of CONFIG_VT, cfr. commit9cbce8d7e1dae0744ca4f68d62aa7de18196b6f4, "console/font: Refactor fontsupport code selection logic").Hence move the fonts and their support logic from drivers/video/console/ toits own library directory lib/fonts/.This also allows to limit processing of drivers/video/console/Makefile toCONFIG_VT=y again.[Kevin Hilman : Update arch/arm/boot/compressed/Makefile]Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/lib/fonts/Makefile