Changes in Kconfig.devices

1e5b5df6 - m68k: /proc/hardware should depend on PROC_FS

Thu, 09 Feb 2023 01:08:25 +0000

m68k: /proc/hardware should depend on PROC_FSWhen CONFIG_PROC_FS is not set, there is a build error for an unusedfunction. Make PROC_HARDWARE depend on PROC_FS to prevent this error.In file included from ../arch/m68k/kernel/setup.c:3:../arch/m68k/kernel/setup_mm.c:477:12: error: 'hardware_proc_show' defined but not used [-Werror=unused-function] 477 | static int hardware_proc_show(struct seq_file *m, void *v) | ^~~~~~~~~~~~~~~~~~Fixes: 66d857b08b8c ("m68k: merge m68k and m68knommu arch directories") # v3.0Signed-off-by: Randy Dunlap Reviewed-by: Geert Uytterhoeven Link: https://lore.kernel.org/r/20230209010825.24136-1-rdunlap@infradead.orgSigned-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/Kconfig.devices

a7f7f624 - treewide: replace '---help---' in Kconfig files with 'help'

Sat, 13 Jun 2020 16:50:22 +0000

treewide: replace '---help---' in Kconfig files with 'help'Since commit 84af7a6194e4 ("checkpatch: kconfig: prefer 'help' over'---help---'"), the number of '---help---' has been graduallydecreasing, but there are still more than 2400 instances.This commit finishes the conversion. While I touched the lines,I also fixed the indentation.There are a variety of indentation styles found. a) 4 spaces + '---help---' b) 7 spaces + '---help---' c) 8 spaces + '---help---' d) 1 space + 1 tab + '---help---' e) 1 tab + '---help---' (correct indentation) f) 1 tab + 1 space + '---help---' g) 1 tab + 2 spaces + '---help---'In order to convert all of them to 1 tab + 'help', I ran thefollowing commend: $ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'Signed-off-by: Masahiro Yamada List of files: /linux-6.15/arch/m68k/Kconfig.devices

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/arch/m68k/Kconfig.devices

2c8faf3d - m68k: AMIGA_BUILTIN_SERIAL should depend on TTY

Sun, 14 Sep 2014 09:42:11 +0000

m68k: AMIGA_BUILTIN_SERIAL should depend on TTYIf CONFIG_TTY=n:drivers/built-in.o: In function `rs_flush_buffer':amiserial.c:(.text+0x1f626): undefined reference to `tty_wakeup'drivers/built-in.o: In function `transmit_chars':amiserial.c:(.text+0x1f6c8): undefined reference to `tty_wakeup'drivers/built-in.o: In function `change_speed':amiserial.c:(.text+0x1f80a): undefined reference to `tty_termios_baud_rate'amiserial.c:(.text+0x1f88c): undefined reference to `tty_termios_baud_rate'drivers/built-in.o: In function `check_modem_status':amiserial.c:(.text+0x1faa6): undefined reference to `tty_hangup'amiserial.c:(.text+0x1faec): undefined reference to `tty_wakeup'drivers/built-in.o: In function `get_serial_info':amiserial.c:(.text+0x1fb88): undefined reference to `tty_lock'amiserial.c:(.text+0x1fbc0): undefined reference to `tty_unlock'drivers/built-in.o: In function `rs_open':amiserial.c:(.text+0x1fdc6): undefined reference to `tty_port_block_til_ready'drivers/built-in.o: In function `set_serial_info':amiserial.c:(.text+0x1fe0c): undefined reference to `tty_lock'amiserial.c:(.text+0x1fea0): undefined reference to `tty_unlock'amiserial.c:(.text+0x1fed0): undefined reference to `tty_unlock'amiserial.c:(.text+0x1ffaa): undefined reference to `tty_unlock'drivers/built-in.o: In function `receive_chars':amiserial.c:(.text+0x2005c): undefined reference to `do_SAK'amiserial.c:(.text+0x200e0): undefined reference to `tty_insert_flip_string_flags'amiserial.c:(.text+0x2013c): undefined reference to `tty_insert_flip_string_flags'amiserial.c:(.text+0x20148): undefined reference to `tty_flip_buffer_push'drivers/built-in.o: In function `rs_close':amiserial.c:(.text+0x20744): undefined reference to `tty_port_close_start'amiserial.c:(.text+0x2078a): undefined reference to `tty_ldisc_flush'amiserial.c:(.text+0x20798): undefined reference to `tty_port_close_end'drivers/built-in.o: In function `amiga_serial_probe':amiserial.c:(.init.text+0x96a): undefined reference to `__tty_alloc_driver'amiserial.c:(.init.text+0x9c0): undefined reference to `tty_std_termios'amiserial.c:(.init.text+0x9e6): undefined reference to `tty_set_operations'amiserial.c:(.init.text+0xa3e): undefined reference to `tty_port_init'amiserial.c:(.init.text+0xa5c): undefined reference to `tty_port_link_device'amiserial.c:(.init.text+0xa6c): undefined reference to `tty_register_driver'amiserial.c:(.init.text+0xb4a): undefined reference to `tty_unregister_driver'amiserial.c:(.init.text+0xb58): undefined reference to `tty_port_destroy'amiserial.c:(.init.text+0xb64): undefined reference to `put_tty_driver'Signed-off-by: Geert Uytterhoeven Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/arch/m68k/Kconfig.devices

fd4d453b - m68k: AMIGA_BUILTIN_SERIAL should depend on TTY

Tue, 09 Sep 2014 09:54:50 +0000

m68k: AMIGA_BUILTIN_SERIAL should depend on TTYIf CONFIG_TTY=n:drivers/built-in.o: In function `rs_flush_buffer':amiserial.c:(.text+0x1f626): undefined reference to `tty_wakeup'drivers/built-in.o: In function `transmit_chars':amiserial.c:(.text+0x1f6c8): undefined reference to `tty_wakeup'drivers/built-in.o: In function `change_speed':amiserial.c:(.text+0x1f80a): undefined reference to `tty_termios_baud_rate'amiserial.c:(.text+0x1f88c): undefined reference to `tty_termios_baud_rate'drivers/built-in.o: In function `check_modem_status':amiserial.c:(.text+0x1faa6): undefined reference to `tty_hangup'amiserial.c:(.text+0x1faec): undefined reference to `tty_wakeup'drivers/built-in.o: In function `get_serial_info':amiserial.c:(.text+0x1fb88): undefined reference to `tty_lock'amiserial.c:(.text+0x1fbc0): undefined reference to `tty_unlock'drivers/built-in.o: In function `rs_open':amiserial.c:(.text+0x1fdc6): undefined reference to `tty_port_block_til_ready'drivers/built-in.o: In function `set_serial_info':amiserial.c:(.text+0x1fe0c): undefined reference to `tty_lock'amiserial.c:(.text+0x1fea0): undefined reference to `tty_unlock'amiserial.c:(.text+0x1fed0): undefined reference to `tty_unlock'amiserial.c:(.text+0x1ffaa): undefined reference to `tty_unlock'drivers/built-in.o: In function `receive_chars':amiserial.c:(.text+0x2005c): undefined reference to `do_SAK'amiserial.c:(.text+0x200e0): undefined reference to `tty_insert_flip_string_flags'amiserial.c:(.text+0x2013c): undefined reference to `tty_insert_flip_string_flags'amiserial.c:(.text+0x20148): undefined reference to `tty_flip_buffer_push'drivers/built-in.o: In function `rs_close':amiserial.c:(.text+0x20744): undefined reference to `tty_port_close_start'amiserial.c:(.text+0x2078a): undefined reference to `tty_ldisc_flush'amiserial.c:(.text+0x20798): undefined reference to `tty_port_close_end'drivers/built-in.o: In function `amiga_serial_probe':amiserial.c:(.init.text+0x96a): undefined reference to `__tty_alloc_driver'amiserial.c:(.init.text+0x9c0): undefined reference to `tty_std_termios'amiserial.c:(.init.text+0x9e6): undefined reference to `tty_set_operations'amiserial.c:(.init.text+0xa3e): undefined reference to `tty_port_init'amiserial.c:(.init.text+0xa5c): undefined reference to `tty_port_link_device'amiserial.c:(.init.text+0xa6c): undefined reference to `tty_register_driver'amiserial.c:(.init.text+0xb4a): undefined reference to `tty_unregister_driver'amiserial.c:(.init.text+0xb58): undefined reference to `tty_port_destroy'amiserial.c:(.init.text+0xb64): undefined reference to `put_tty_driver'Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/Kconfig.devices

1a84db56 - treewide: fix errors in printk

Fri, 29 Aug 2014 14:37:33 +0000

treewide: fix errors in printkThis patch fix spelling typo in printk.Signed-off-by: Masanari Iida Acked-by: Geert Uytterhoeven Acked-by: Randy Dunlap Signed-off-by: Jiri Kosina List of files: /linux-6.15/arch/m68k/Kconfig.devices

1d87a8f2 - m68k/atari: EtherNEC - add platform device support

Sat, 06 Apr 2013 00:26:40 +0000

m68k/atari: EtherNEC - add platform device supportAdd platform device for the Atari ROM port ethernet adapter, EtherNEC.This platform device will be used by the ne.c driver.[Geert] Conditionalize platform device data structuresSigned-off-by: Michael Schmitz Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/Kconfig.devices

736b24db - m68k/atari: EtherNAT - platform device and IRQ support code

Sat, 06 Apr 2013 00:26:39 +0000

m68k/atari: EtherNAT - platform device and IRQ support codeAdd platform device and interrupt definitions necessary for the EtherNATEthernet/USB adapter for the Falcon extension port. EtherNAT interruptnumbers are 139/140 so the max. interrupt number for Atari has to beincreased.[Geert] Conditionalize platform device data structuresSigned-off-by: Michael Schmitz Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/Kconfig.devices

4f73bc4d - tty: Added a CONFIG_TTY option to allow removal of TTY

Fri, 18 Jan 2013 06:44:22 +0000

tty: Added a CONFIG_TTY option to allow removal of TTYThe option allows you to remove TTY and compile without errors. Thissaves space on systems that won't support TTY interfaces anyway.bloat-o-meter output is below.The bulk of this patch consists of Kconfig changes adding "depends onTTY" to various serial devices and similar drivers that require the TTYlayer. Ideally, these dependencies would occur on a common intermediatesymbol such as SERIO, but most drivers "select SERIO" rather than"depends on SERIO", and "select" does not respect dependencies.bloat-o-meter output comparing our previous minimal to new minimal byremoving TTY. The list is filtered to not show removed entries with awk'$3 != "-"' as the list was very long.add/remove: 0/226 grow/shrink: 2/14 up/down: 6/-35356 (-35350)function old new deltachr_dev_init 166 170 +4allow_signal 80 82 +2static.__warned 143 142 -1disallow_signal 63 62 -1__set_special_pids 95 94 -1unregister_console 126 121 -5start_kernel 546 541 -5register_console 593 588 -5copy_from_user 45 40 -5sys_setsid 128 120 -8sys_vhangup 32 19 -13do_exit 1543 1526 -17bitmap_zero 60 40 -20arch_local_irq_save 137 117 -20release_task 674 652 -22static.spin_unlock_irqrestore 308 260 -48Signed-off-by: Joe Millenbach Reviewed-by: Jamey Sharp Reviewed-by: Josh Triplett Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/arch/m68k/Kconfig.devices

112f8b12 - arch/m68k: remove CONFIG_EXPERIMENTAL

Tue, 23 Oct 2012 20:01:27 +0000

arch/m68k: remove CONFIG_EXPERIMENTALThis config item has not carried much meaning for a while now and isalmost always enabled by default. As agreed during the Linux kernelsummit, remove it.CC: Geert Uytterhoeven Signed-off-by: Kees Cook Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/Kconfig.devices

3bd9e50b - m68k/mac: Make CONFIG_HEARTBEAT unavailable on Mac

Thu, 29 Dec 2011 19:00:31 +0000

m68k/mac: Make CONFIG_HEARTBEAT unavailable on Macmac_heartbeat() was never really implemented.Signed-off-by: Geert Uytterhoeven Acked-by: Greg Ungerer List of files: /linux-6.15/arch/m68k/Kconfig.devices

176f2934 - m68k/serial: Remove references to obsolete serial config options

Tue, 06 Dec 2011 20:16:13 +0000

m68k/serial: Remove references to obsolete serial config options - ATARI_MFPSER, ATARI_MIDI, MULTIFACE_III_TTY, and DN_SERIAL have no corresponding drivers (anymore), - Clean up SERIAL_CONSOLE dependencies and help text.Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/Kconfig.devices

1d9532b3 - m68k/serial: Remove references to obsolete CONFIG_SERIAL167

Tue, 08 Nov 2011 22:30:19 +0000

m68k/serial: Remove references to obsolete CONFIG_SERIAL167commit 51c9d654c2def97827395a7fbfd0c6f865c26544 ("Staging: delete ttydrivers") removed the MVME167 serial driver, but forgot to remove thesereferences.Signed-off-by: Geert Uytterhoeven List of files: /linux-6.15/arch/m68k/Kconfig.devices

24ed6ddd - m68k: Revive lost ARAnyM config options

Tue, 25 Oct 2011 19:14:10 +0000

m68k: Revive lost ARAnyM config optionscommit 0e152d80507b75c00aac60f2ffc586360687cd52 ("m68k: reorganize Kconfigoptions to improve mmu/non-mmu selections") accidentally dropped the ARAnyMconfig options. Re-add them to the "Platform devices" section.Signed-off-by: Geert Uytterhoeven Acked-by: Greg Ungerer List of files: /linux-6.15/arch/m68k/Kconfig.devices

dbcbf588 - m68k: drop unused Kconfig symbols

Fri, 21 Oct 2011 05:15:20 +0000

m68k: drop unused Kconfig symbolsReported-by: Geert Uytterhoeven Signed-off-by: Paul Bolle Signed-off-by: Greg Ungerer List of files: /linux-6.15/arch/m68k/Kconfig.devices

95e82747 - m68k: drop unused Kconfig symbols

Tue, 18 Oct 2011 08:10:07 +0000

m68k: drop unused Kconfig symbolsSigned-off-by: Paul Bolle Acked-by: Geert Uytterhoeven Signed-off-by: Greg Ungerer List of files: /linux-6.15/arch/m68k/Kconfig.devices

0e152d80 - m68k: reorganize Kconfig options to improve mmu/non-mmu selections

Mon, 20 Jun 2011 05:49:09 +0000

m68k: reorganize Kconfig options to improve mmu/non-mmu selectionsThe current mmu and non-mmu Kconfig files can be merged to forma more general selection of options. The current break up of optionsis due to the simple brute force merge from the m68k and m68knommuarch directories.Many of the options are not at all specific to having the MMU enabledor not. They are actually associated with a particular CPU type orplatform type.Ultimately as we support all processors with the MMU disabled we needmany of these options to be selectable without the MMU option enabled.And likewise some of the ColdFire processors, which currently are onlysupported with the MMU disabled, do have MMU hardware, and will needto have options selected on CPU type, not MMU disabled.This patch removes the old mmu and non-mmu Kconfigs and instead breaksup the configuration into four areas: cpu, machine, bus, devices.The Kconfig.cpu lists all the options associated with selecting a CPU,and includes options specific to each CPU type as well.Kconfig.machine lists all options associated with selecting a machinetype. Almost always the machines selectable is restricted by the chosenCPU.Kconfig.bus contains options associated with selecting bus types on thevarious machine types. That includes PCI bus, PCMCIA bus, etc.Kconfig.devices contains options for drivers and driver associatedoptions.Signed-off-by: Greg Ungerer List of files: /linux-6.15/arch/m68k/Kconfig.devices