.gitignore: add SPDX License IdentifierAdd SPDX License Identifier to all .gitignore files.Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfou
.gitignore: add SPDX License IdentifierAdd SPDX License Identifier to all .gitignore files.Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
show more ...
leds: core: Add support for composing LED class device namesAdd generic support for composing LED class device name. The newlyintroduced led_compose_name() function composes device name according
leds: core: Add support for composing LED class device namesAdd generic support for composing LED class device name. The newlyintroduced led_compose_name() function composes device name accordingto either <color:function> or <devicename:color:function> pattern,depending on the configuration of initialization data.Backward compatibility with in-driver hard-coded LED class devicenames is assured thanks to the default_label and devicename propertiesof newly introduced struct led_init_data.In case none of the aforementioned properties was found, then, for OFnodes, the node name is adopted for LED class device name.At the occassion of amending the Documentation/leds/leds-class.txtunify spelling: colour -> color.Alongside these changes added is a new tool - tools/leds/get_led_device_info.sh.The tool allows retrieving details of a LED class device's parent device,which proves that using vendor or product name for devicename partof LED name doesn't convey any added value since that information had beenalready available in sysfs. The script performs also basic validationof a LED class device name.Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>Cc: Baolin Wang <baolin.wang@linaro.org>Cc: Dan Murphy <dmurphy@ti.com>Cc: Daniel Mack <daniel@zonque.org>Cc: Linus Walleij <linus.walleij@linaro.org>Cc: Oleh Kravchenko <oleg@kaa.org.ua>Cc: Sakari Ailus <sakari.ailus@linux.intel.com>Cc: Simon Shields <simon@lineageos.org>Reviewed-by: Linus Walleij <linus.walleij@linaro.org>Acked-by: Pavel Machek <pavel@ucw.cz>
tools: fix cross-compile var clobberingCurrently a number of Makefiles break when used with toolchains thatpass extra flags in CC and other cross-compile related variables (suchas --sysroot).Th
tools: fix cross-compile var clobberingCurrently a number of Makefiles break when used with toolchains thatpass extra flags in CC and other cross-compile related variables (suchas --sysroot).Thus we get this error when we use a toolchain that puts --sysroot inthe CC var: ~/src/linux/tools$ make iio [snip] iio_event_monitor.c:18:10: fatal error: unistd.h: No such file or directory #include <unistd.h> ^~~~~~~~~~This occurs because we clobber several env vars related tocross-compiling with lines like this: CC = $(CROSS_COMPILE)gccAlthough this will point to a valid cross-compiler, we lose any extraflags that might exist in the CC variable, which can break toolchainsthat rely on them (for example, those that use --sysroot).This easily shows up using a Yocto SDK: $ . [snip]/sdk/environment-setup-cortexa8hf-neon-poky-linux-gnueabi $ echo $CC arm-poky-linux-gnueabi-gcc -march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 --sysroot=[snip]/sdk/sysroots/cortexa8hf-neon-poky-linux-gnueabi $ echo $CROSS_COMPILE arm-poky-linux-gnueabi- $ echo ${CROSS_COMPILE}gcc krm-poky-linux-gnueabi-gccAlthough arm-poky-linux-gnueabi-gcc is a cross-compiler, we've lost the--sysroot and other flags that enable us to find the right libraries tolink against, so we can't find unistd.h and other libraries and headers.Normally with the --sysroot flag we would find unistd.h in the sdkdirectory in the sysroot: $ find [snip]/sdk/sysroots -path '*/usr/include/unistd.h' [snip]/sdk/sysroots/cortexa8hf-neon-poky-linux-gnueabi/usr/include/unistd.hThe perf Makefile adds CC = $(CROSS_COMPILE)gcc if and only if CC is notalready set, and it compiles correctly with the above toolchain.So, generalize the logic that perf uses in the common Makefile andremove the manual CC = $(CROSS_COMPILE)gcc lines from each Makefile.Note that this patch does not fix cross-compile for all the tools (somehave other bugs), but it does fix it for all except usb and acpi, whichstill have other unrelated issues.I tested both with and without the patch on native and cross-build andthere appear to be no regressions.Link: http://lkml.kernel.org/r/20180107214028.23771-1-martin@martingkelly.comSigned-off-by: Martin Kelly <martin@martingkelly.com>Acked-by: Mark Brown <broonie@kernel.org>Cc: Tejun Heo <tj@kernel.org>Cc: Li Zefan <lizefan@huawei.com>Cc: Johannes Weiner <hannes@cmpxchg.org>Cc: Linus Walleij <linus.walleij@linaro.org>Cc: "K. Y. Srinivasan" <kys@microsoft.com>Cc: Haiyang Zhang <haiyangz@microsoft.com>Cc: Stephen Hemminger <sthemmin@microsoft.com>Cc: Jonathan Cameron <jic23@kernel.org>Cc: Pali Rohar <pali.rohar@gmail.com>Cc: Richard Purdie <rpurdie@rpsys.net>Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>Cc: Pavel Machek <pavel@ucw.cz>Cc: Peter Zijlstra <peterz@infradead.org>Cc: Ingo Molnar <mingo@redhat.com>Cc: Arnaldo Carvalho de Melo <acme@kernel.org>Cc: Robert Moore <robert.moore@intel.com>Cc: Lv Zheng <lv.zheng@intel.com>Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>Cc: Valentina Manea <valentina.manea.m@gmail.com>Cc: Shuah Khan <shuah@kernel.org>Cc: Mario Limonciello <mario.limonciello@dell.com>Signed-off-by: Andrew Morton <akpm@linux-foundation.org>Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
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>
tools/leds: Add led_hw_brightness_mon programLED subsystem supports POLLPRI on "brightness_hw_changed" sysfs fileof LED class devices. This tool demonstrates how to use the feature.Signed-off-by
tools/leds: Add led_hw_brightness_mon programLED subsystem supports POLLPRI on "brightness_hw_changed" sysfs fileof LED class devices. This tool demonstrates how to use the feature.Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>Acked-by: Hans de Goede <hdegoede@redhat.com>Acked-by: Pavel Machek <pavel@ucw.cz>
tools/leds: Add uledmon program for monitoring userspace LEDsThe uleds driver provides userspace LED devices. This tool is used tocreate one of these devices and monitor the changes in brighness f
tools/leds: Add uledmon program for monitoring userspace LEDsThe uleds driver provides userspace LED devices. This tool is used tocreate one of these devices and monitor the changes in brighness fortesting purposes.Signed-off-by: David Lechner <david@lechnology.com>Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>