Changes in Makefile

6cccb3bb - s390/net: Remove LCS driver

Tue, 04 Feb 2025 10:31:35 +0000

s390/net: Remove LCS driverThe original Open Systems Adapter (OSA) was introduced by IBM in themid-90s. These were then superseded by OSA-Express in 1999 which usedQueued Direct IO to greatly improve throughput. The newer cardsretained the older, slower non-QDIO (OSE) modes for compatibility witholder systems. In Linux, the lcs driver was responsible for cardsoperating in the older OSE mode and the qeth driver was introduced toallow the OSA-Express cards to operate in the newer QDIO (OSD) mode.For an S390 machine from 1998 or later, there is no reason to use theOSE mode and lcs driver as all OSA cards since 1999 provide the fasterOSD mode. As a result, it's been years since we have heard of acustomer configuration involving the lcs driver.This patch removes the lcs driver. The technology it supports has beenobsolete for past 25+ years and is irrelevant for current use cases.Reviewed-by: Alexandra Winter Acked-by: Heiko Carstens Acked-by: Peter Oberparleiter Signed-off-by: Aswin Karuvally Signed-off-by: Alexandra Winter Reviewed-by: Simon Horman Link: https://patch.msgid.link/20250204103135.1619097-1-wintera@linux.ibm.comSigned-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/s390/net/Makefile

d896ac62 - s390/qeth: move ethtool code into its own file

Fri, 15 Feb 2019 18:22:28 +0000

s390/qeth: move ethtool code into its own fileMost of this is self-contained code.Signed-off-by: Julian Wiedmann Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/s390/net/Makefile

684b89bc - s390/ism: add device driver for internal shared memory

Thu, 28 Jun 2018 17:05:13 +0000

s390/ism: add device driver for internal shared memoryAdd support for the Internal Shared Memory vPCI Adapter.This driver implements the interfaces of the SMC-D protocol.Signed-off-by: Sebastian Ott Signed-off-by: Ursula Braun Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/s390/net/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/drivers/s390/net/Makefile

83650a2e - s390: remove claw driver

Fri, 27 Feb 2015 11:52:32 +0000

s390: remove claw driverclaw devices are outdated and no longer supported.This patch removes the claw driver.Signed-off-by: Ursula Braun Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/s390/net/Makefile

b4d72c08 - qeth: bridgeport support - basic control

Tue, 14 Jan 2014 14:54:11 +0000

qeth: bridgeport support - basic controlIntroduce functions to assign roles and check state of bridgeport-capableHiperSocket devices, and sysfs attributes providing access to thesefunctions from userspace. Introduce udev events emitted when the stateof a bridgeport device changes.Signed-off-by: Eugene Crosser Signed-off-by: Frank Blaschka Reviewed-by: Ursula Braun Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/s390/net/Makefile

1ffaa640 - [S390] smsgiucv_app: deliver z/VM CP special messages (SMSG) as uevents

Mon, 08 Mar 2010 11:26:26 +0000

[S390] smsgiucv_app: deliver z/VM CP special messages (SMSG) as ueventsThe smsgiucv_app driver registers a callback with the smsgiucv driverto receive z/VM CP special messages (SMSG) starting with "APP".When the callback is called for special messages, the driver createsan uevent for the received message. The uevent consists of additionalenvironment data containing the message prefix ("APP"), message sender,and message content.udev rules can be used to trigger application specific actions throughmatching the content or sender of the special message.Signed-off-by: Hendrik Brueckner Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/drivers/s390/net/Makefile

0ca8cc6f - s390: remove cu3088 layer for lcs and ctcm

Thu, 12 Nov 2009 21:46:29 +0000

s390: remove cu3088 layer for lcs and ctcmThe cu3088-driver used as common base for lcs- and ctcm-devicesmakes it difficult to assign the appropriate driver to an lcs-deviceor a ctcm-device. This patch eliminates the cu3088-driver and thusthe root device "cu3088". Path /sys/devices/cu3088 is replaced withthe pathes /sys/devices/lcs and /sys/devices/ctcm.Patch is based on a proposal from Cornelia Huck.Cc: Cornelia Huck Signed-off-by: Ursula Braun Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/s390/net/Makefile

64ef8957 - qeth: remove EDDP

Tue, 24 Mar 2009 20:57:16 +0000

qeth: remove EDDPPerformance measurements showed EDDP does not lower CPU costs but increasethem. So we dump out EDDP code from qeth driver.Signed-off-by: Frank Blaschka Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/s390/net/Makefile

4a71df50 - qeth: new qeth device driver

Fri, 15 Feb 2008 08:19:42 +0000

qeth: new qeth device driverList of major changes and improvements: no manipulation of the global ARP constructor clean code split into core, layer 2 and layer 3 functionality better exploitation of the ethtool interface better representation of the various hardware capabilities fix packet socket support (tcpdump), no fake_ll required osasnmpd notification via udev events coding style and beautificationSigned-off-by: Frank Blaschka Signed-off-by: Jeff Garzik List of files: /linux-6.15/drivers/s390/net/Makefile

293d984f - ctcm: infrastructure for replaced ctc driver

Thu, 07 Feb 2008 23:03:49 +0000

ctcm: infrastructure for replaced ctc driverctcm driver supports the channel-to-channel connections of theold ctc driver plus an additional MPC protocol to provide SNAconnectivity.This new ctcm driver replaces the existing ctc driver.Signed-off-by: Peter Tiedemann Signed-off-by: Ursula Braun Signed-off-by: Jeff Garzik List of files: /linux-6.15/drivers/s390/net/Makefile

33a67fe8 - [S390]: Rewrite of the IUCV base code, part 1

Thu, 08 Feb 2007 21:36:44 +0000

[S390]: Rewrite of the IUCV base code, part 1Remove the old IUCV code from drivers/s390/netRemove approprirate IUCV entries from drivers/s390/net/Makefile,drivers/s390/net/Kconfig and arch/s390/defconfigSigned-off-by: Frank Pavlic Signed-off-by: Martin Schwidefsky Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/s390/net/Makefile

f449c565 - [PATCH] s390: Makefile cleanup

Fri, 15 Sep 2006 14:25:39 +0000

[PATCH] s390: Makefile cleanup[PATCH 3/9] s390: Makefile cleanupFrom: Frank Pavlic remove CONFIG_MPC from Makefile which was introduced accidently in the past.Signed-off-by: Frank Pavlic Signed-off-by: Jeff Garzik List of files: /linux-6.15/drivers/s390/net/Makefile

56347a2e - [PATCH] s390: remove tty support from ctc network device driver [1/2]

Thu, 13 Apr 2006 18:19:12 +0000

[PATCH] s390: remove tty support from ctc network device driver [1/2]Hi jeff,after the first shot I sent to you did not apply Iresend two new patches I've made today to remove tty from ctc network driver.Please apply ....Thank you ...FrankFrom: Peter Tiedemann [1/2]: tty support code will be removed from the ctc network device driver. Today we have a couple of alternatives which are performing much better. The second thing is that ctc should be a network device driver only. We should not mix tty and networking here. This first patch will remove the tty code from ctcmain.c . It also removes the build entry from the Makefile as well as TTY definitions from ctcmain.h. The second patch will remove two files, ctctty.c and ctctty.h.Signed-off-by: Frank Pavlic Signed-off-by: Jeff Garzik List of files: /linux-6.15/drivers/s390/net/Makefile

05e08a2a - [PATCH] s390: qeth bug fixes

Thu, 12 May 2005 18:39:09 +0000

[PATCH] s390: qeth bug fixes[patch 10/10] s390: qeth bug fixes.From: Frank Pavlic qeth network driver related changes: - due to OSA hardware changes in TCP Segmentation Offload support we are able now to pack TSO packets too. This fits perfectly in design of qeth buffer handling and sending data respectively. - remove skb_realloc_headroom from the sending path since hard_header_len value provides enough headroom now. - device recovery behaviour improvement - bug fixed in Enhanced Device Driver Packing functionalitySigned-off-by: Frank Pavlic List of files: /linux-6.15/drivers/s390/net/Makefile

321de3c8 - [PATCH] s390: claw driver wiring

Thu, 12 May 2005 18:17:46 +0000

[PATCH] s390: claw driver wiring[patch 1/10] s390: claw driver wiring.From: Andy Richter claw network driver changes: - Add an entry to the drivers/s390/net Makefile to build the claw driver. - Add claw channel type to cu3088.Signed-off-by: Frank Pavlic List of files: /linux-6.15/drivers/s390/net/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/drivers/s390/net/Makefile