License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license 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 binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the 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 cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base 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 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately 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 license
identifiers 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 the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version 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 correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate 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>
2017-11-01 17:07:57 +03:00
# SPDX-License-Identifier: GPL-2.0
2005-04-17 02:20:36 +04:00
#
# Makefile for linux/drivers/scsi
#
# 30 May 2000, Christoph Hellwig <hch@infradead.org>
# Rewritten to use lists instead of if-statements.
#
# 20 Sep 2000, Torben Mathiasen <tmm@image.dk>
# Changed link order to reflect new scsi initialization.
#
# *!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!
# The link order must be, SCSI Core, SCSI HBA drivers, and
# lastly SCSI peripheral drivers (disk/tape/cdrom/etc.) to
# satisfy certain initialization assumptions in the SCSI layer.
# *!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!*!
CFLAGS_aha152x.o = -DAHA152X_STAT -DAUTOCONF
2007-12-07 16:36:23 +03:00
obj-$(CONFIG_PCMCIA) += pcmcia/
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI) += scsi_mod.o
2021-07-24 10:20:28 +03:00
obj-$(CONFIG_SCSI_COMMON) += scsi_common.o
2005-04-17 02:20:36 +04:00
[SCSI] embryonic RAID class
The idea behind a RAID class is to provide a uniform interface to all
RAID subsystems (both hardware and software) in the kernel.
To do that, I've made this class a transport class that's entirely
subsystem independent (although the matching routines have to match per
subsystem, as you'll see looking at the code). I put it in the scsi
subdirectory purely because I needed somewhere to play with it, but it's
not a scsi specific module.
I used a fusion raid card as the test bed for this; with that kind of
card, this is the type of class output you get:
jejb@titanic> ls -l /sys/class/raid_devices/20\:0\:0\:0/
total 0
lrwxrwxrwx 1 root root 0 Aug 16 17:21 component-0 -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:1:0/20:1:0:0/
lrwxrwxrwx 1 root root 0 Aug 16 17:21 component-1 -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:1:1/20:1:1:0/
lrwxrwxrwx 1 root root 0 Aug 16 17:21 device -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:0:0/20:0:0:0/
-r--r--r-- 1 root root 16384 Aug 16 17:21 level
-r--r--r-- 1 root root 16384 Aug 16 17:21 resync
-r--r--r-- 1 root root 16384 Aug 16 17:21 state
So it's really simple: for a SCSI device representing a hardware raid,
it shows the raid level, the array state, the resync % complete (if the
state is resyncing) and the underlying components of the RAID (these are
exposed in fusion on the virtual channel 1).
As you can see, this type of information can be exported by almost
anything, including software raid.
The more difficult trick, of course, is going to be getting it to
perform configuration type actions with writable attributes.
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
2005-08-17 03:27:34 +04:00
obj-$(CONFIG_RAID_ATTRS) += raid_class.o
2005-04-17 02:20:36 +04:00
# --- NOTE ORDERING HERE ---
# For kernel non-modular link, transport attributes need to
# be initialised before drivers
# --------------------------
obj-$(CONFIG_SCSI_SPI_ATTRS) += scsi_transport_spi.o
obj-$(CONFIG_SCSI_FC_ATTRS) += scsi_transport_fc.o
obj-$(CONFIG_SCSI_ISCSI_ATTRS) += scsi_transport_iscsi.o
2005-09-09 18:22:50 +04:00
obj-$(CONFIG_SCSI_SAS_ATTRS) += scsi_transport_sas.o
2006-08-29 18:22:51 +04:00
obj-$(CONFIG_SCSI_SAS_LIBSAS) += libsas/
2007-06-27 11:32:39 +04:00
obj-$(CONFIG_SCSI_SRP_ATTRS) += scsi_transport_srp.o
2008-05-02 01:49:46 +04:00
obj-$(CONFIG_SCSI_DH) += device_handler/
2005-04-17 02:20:36 +04:00
2008-12-10 02:10:17 +03:00
obj-$(CONFIG_LIBFC) += libfc/
2009-03-17 21:42:13 +03:00
obj-$(CONFIG_LIBFCOE) += fcoe/
2008-12-10 02:10:24 +03:00
obj-$(CONFIG_FCOE) += fcoe/
2009-04-18 05:33:26 +04:00
obj-$(CONFIG_FCOE_FNIC) += fnic/
2015-05-29 11:04:01 +03:00
obj-$(CONFIG_SCSI_SNIC) += snic/
2011-02-04 23:10:34 +03:00
obj-$(CONFIG_SCSI_BNX2X_FCOE) += libfc/ fcoe/ bnx2fc/
2017-02-15 17:28:23 +03:00
obj-$(CONFIG_QEDF) += qedf/
2008-12-02 09:32:12 +03:00
obj-$(CONFIG_ISCSI_TCP) += libiscsi.o libiscsi_tcp.o iscsi_tcp.o
2006-05-11 11:03:30 +04:00
obj-$(CONFIG_INFINIBAND_ISER) += libiscsi.o
2010-08-02 21:46:12 +04:00
obj-$(CONFIG_ISCSI_BOOT_SYSFS) += iscsi_boot_sysfs.o
2007-06-17 16:47:08 +04:00
obj-$(CONFIG_SCSI_A4000T) += 53c700.o a4000t.o
2007-06-17 16:47:09 +04:00
obj-$(CONFIG_SCSI_ZORRO7XX) += 53c700.o zorro7xx.o
2018-04-12 04:53:26 +03:00
obj-$(CONFIG_SCSI_ZORRO_ESP) += esp_scsi.o zorro_esp.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_A3000_SCSI) += a3000.o wd33c93.o
obj-$(CONFIG_A2091_SCSI) += a2091.o wd33c93.o
obj-$(CONFIG_GVP11_SCSI) += gvp11.o wd33c93.o
obj-$(CONFIG_MVME147_SCSI) += mvme147.o wd33c93.o
obj-$(CONFIG_SGIWD93_SCSI) += sgiwd93.o wd33c93.o
obj-$(CONFIG_ATARI_SCSI) += atari_scsi.o
obj-$(CONFIG_MAC_SCSI) += mac_scsi.o
2008-04-25 19:06:05 +04:00
obj-$(CONFIG_SCSI_MAC_ESP) += esp_scsi.o mac_esp.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SUN3_SCSI) += sun3_scsi.o sun3_scsi_vme.o
2007-06-17 16:47:07 +04:00
obj-$(CONFIG_MVME16x_SCSI) += 53c700.o mvme16x_scsi.o
2007-06-17 16:47:06 +04:00
obj-$(CONFIG_BVME6000_SCSI) += 53c700.o bvme6000_scsi.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_SIM710) += 53c700.o sim710.o
obj-$(CONFIG_SCSI_ADVANSYS) += advansys.o
obj-$(CONFIG_SCSI_BUSLOGIC) += BusLogic.o
2006-07-12 19:59:32 +04:00
obj-$(CONFIG_SCSI_ARCMSR) += arcmsr/
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_AHA152X) += aha152x.o
obj-$(CONFIG_SCSI_AHA1542) += aha1542.o
obj-$(CONFIG_SCSI_AHA1740) += aha1740.o
obj-$(CONFIG_SCSI_AIC7XXX) += aic7xxx/
obj-$(CONFIG_SCSI_AIC79XX) += aic7xxx/
obj-$(CONFIG_SCSI_AACRAID) += aacraid/
2006-08-29 18:22:51 +04:00
obj-$(CONFIG_SCSI_AIC94XX) += aic94xx/
2009-10-14 12:19:21 +04:00
obj-$(CONFIG_SCSI_PM8001) += pm8001/
2011-07-03 09:56:22 +04:00
obj-$(CONFIG_SCSI_ISCI) += isci/
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_IPS) += ips.o
2019-05-14 20:23:07 +03:00
obj-$(CONFIG_SCSI_FDOMAIN) += fdomain.o
2019-05-14 20:23:08 +03:00
obj-$(CONFIG_SCSI_FDOMAIN_PCI) += fdomain_pci.o
2019-05-14 20:23:09 +03:00
obj-$(CONFIG_SCSI_FDOMAIN_ISA) += fdomain_isa.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_GENERIC_NCR5380) += g_NCR5380.o
obj-$(CONFIG_SCSI_QLOGIC_FAS) += qlogicfas408.o qlogicfas.o
obj-$(CONFIG_PCMCIA_QLOGIC) += qlogicfas408.o
obj-$(CONFIG_SCSI_QLOGIC_1280) += qla1280.o
2006-01-09 21:17:40 +03:00
obj-$(CONFIG_SCSI_QLA_FC) += qla2xxx/
2011-09-01 02:02:00 +04:00
obj-$(CONFIG_SCSI_QLA_ISCSI) += libiscsi.o qla4xxx/
2005-04-18 01:05:31 +04:00
obj-$(CONFIG_SCSI_LPFC) += lpfc/
2021-06-02 02:55:12 +03:00
obj-$(CONFIG_SCSI_EFCT) += elx/
2009-09-24 04:46:15 +04:00
obj-$(CONFIG_SCSI_BFA_FC) += bfa/
2012-11-15 21:11:18 +04:00
obj-$(CONFIG_SCSI_CHELSIO_FCOE) += csiostor/
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_DMX3191D) += dmx3191d.o
2009-12-09 01:09:11 +03:00
obj-$(CONFIG_SCSI_HPSA) += hpsa.o
2016-06-28 00:41:00 +03:00
obj-$(CONFIG_SCSI_SMARTPQI) += smartpqi/
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_SYM53C8XX_2) += sym53c8xx_2/
obj-$(CONFIG_SCSI_ZALON) += zalon7xx.o
obj-$(CONFIG_SCSI_DC395x) += dc395x.o
2014-11-24 17:37:25 +03:00
obj-$(CONFIG_SCSI_AM53C974) += esp_scsi.o am53c974.o
2015-06-10 01:15:52 +03:00
obj-$(CONFIG_CXLFLASH) += cxlflash/
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_MEGARAID_LEGACY) += megaraid.o
obj-$(CONFIG_MEGARAID_NEWGEN) += megaraid/
2005-09-21 01:46:58 +04:00
obj-$(CONFIG_MEGARAID_SAS) += megaraid/
2012-11-30 06:14:21 +04:00
obj-$(CONFIG_SCSI_MPT3SAS) += mpt3sas/
2021-05-20 18:25:22 +03:00
obj-$(CONFIG_SCSI_MPI3MR) += mpi3mr/
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_ACARD) += atp870u.o
2007-05-23 10:48:10 +04:00
obj-$(CONFIG_SCSI_SUNESP) += esp_scsi.o sun_esp.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_INITIO) += initio.o
obj-$(CONFIG_SCSI_INIA100) += a100u2w.o
obj-$(CONFIG_SCSI_QLOGICPTI) += qlogicpti.o
obj-$(CONFIG_SCSI_MESH) += mesh.o
obj-$(CONFIG_SCSI_MAC53C94) += mac53c94.o
2018-10-17 18:25:11 +03:00
obj-$(CONFIG_SCSI_MYRB) += myrb.o
2018-10-17 18:25:12 +03:00
obj-$(CONFIG_SCSI_MYRS) += myrs.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_BLK_DEV_3W_XXXX_RAID) += 3w-xxxx.o
obj-$(CONFIG_SCSI_3W_9XXX) += 3w-9xxx.o
2009-10-24 01:52:33 +04:00
obj-$(CONFIG_SCSI_3W_SAS) += 3w-sas.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_PPA) += ppa.o
obj-$(CONFIG_SCSI_IMM) += imm.o
2007-05-22 12:13:19 +04:00
obj-$(CONFIG_JAZZ_ESP) += esp_scsi.o jazz_esp.o
2008-02-01 02:13:34 +03:00
obj-$(CONFIG_SUN3X_ESP) += esp_scsi.o sun3x_esp.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_LASI700) += 53c700.o lasi700.o
2006-12-25 23:32:04 +03:00
obj-$(CONFIG_SCSI_SNI_53C710) += 53c700.o sni_53c710.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_SCSI_NSP32) += nsp32.o
obj-$(CONFIG_SCSI_IPR) += ipr.o
obj-$(CONFIG_SCSI_IBMVSCSI) += ibmvscsi/
2016-06-29 01:05:35 +03:00
obj-$(CONFIG_SCSI_IBMVSCSIS) += ibmvscsi_tgt/
2008-07-01 22:14:30 +04:00
obj-$(CONFIG_SCSI_IBMVFC) += ibmvscsi/
2006-05-16 10:38:09 +04:00
obj-$(CONFIG_SCSI_HPTIOP) += hptiop.o
2006-09-01 11:12:19 +04:00
obj-$(CONFIG_SCSI_STEX) += stex.o
2009-05-09 00:35:37 +04:00
obj-$(CONFIG_SCSI_MVSAS) += mvsas/
2011-05-11 19:22:44 +04:00
obj-$(CONFIG_SCSI_MVUMI) += mvumi.o
2007-07-21 15:37:47 +04:00
obj-$(CONFIG_PS3_ROM) += ps3rom.o
2010-08-17 07:55:53 +04:00
obj-$(CONFIG_SCSI_CXGB3_ISCSI) += libiscsi.o libiscsi_tcp.o cxgbi/
2010-08-17 07:55:53 +04:00
obj-$(CONFIG_SCSI_CXGB4_ISCSI) += libiscsi.o libiscsi_tcp.o cxgbi/
2009-06-09 05:14:44 +04:00
obj-$(CONFIG_SCSI_BNX2_ISCSI) += libiscsi.o bnx2i/
2016-12-01 11:21:08 +03:00
obj-$(CONFIG_QEDI) += libiscsi.o qedi/
2009-09-05 06:06:35 +04:00
obj-$(CONFIG_BE2ISCSI) += libiscsi.o be2iscsi/
2013-08-23 18:35:45 +04:00
obj-$(CONFIG_SCSI_ESAS2R) += esas2r/
2009-08-26 04:35:18 +04:00
obj-$(CONFIG_SCSI_PMCRAID) += pmcraid.o
2012-02-05 15:16:00 +04:00
obj-$(CONFIG_SCSI_VIRTIO) += virtio_scsi.o
2009-10-14 01:51:05 +04:00
obj-$(CONFIG_VMWARE_PVSCSI) += vmw_pvscsi.o
2014-08-28 08:44:11 +04:00
obj-$(CONFIG_XEN_SCSI_FRONTEND) += xen-scsifront.o
2012-02-10 02:14:48 +04:00
obj-$(CONFIG_HYPERV_STORAGE) += hv_storvsc.o
2014-11-25 01:24:41 +03:00
obj-$(CONFIG_SCSI_WD719X) += wd719x.o
2005-04-17 02:20:36 +04:00
obj-$(CONFIG_ARM) += arm/
obj-$(CONFIG_CHR_DEV_ST) += st.o
obj-$(CONFIG_BLK_DEV_SD) += sd_mod.o
obj-$(CONFIG_BLK_DEV_SR) += sr_mod.o
obj-$(CONFIG_CHR_DEV_SG) += sg.o
2005-05-10 12:59:13 +04:00
obj-$(CONFIG_CHR_DEV_SCH) += ch.o
2008-02-04 00:48:56 +03:00
obj-$(CONFIG_SCSI_ENCLOSURE) += ses.o
2005-04-17 02:20:36 +04:00
2015-11-17 19:50:30 +03:00
obj-$(CONFIG_SCSI_HISI_SAS) += hisi_sas/
2009-01-25 18:24:14 +03:00
2006-03-23 04:39:38 +03:00
# This goes last, so that "real" scsi devices probe earlier
obj-$(CONFIG_SCSI_DEBUG) += scsi_debug.o
2015-01-08 09:43:48 +03:00
scsi_mod-y += scsi.o hosts.o scsi_ioctl.o \
2007-07-09 22:59:59 +04:00
scsicam.o scsi_error.o scsi_lib.o
2015-01-08 09:43:48 +03:00
scsi_mod-$(CONFIG_SCSI_CONSTANTS) += constants.o
2007-07-09 22:59:59 +04:00
scsi_mod-$(CONFIG_SCSI_DMA) += scsi_lib_dma.o
scsi_mod-y += scsi_scan.o scsi_sysfs.o scsi_devinfo.o
[SCSI] SCSI and FC Transport: add netlink support for posting of transport events
This patch formally adds support for the posting of FC events via netlink.
It is a followup to the original RFC at:
http://marc.theaimsgroup.com/?l=linux-scsi&m=114530667923464&w=2
and the initial posting at:
http://marc.theaimsgroup.com/?l=linux-scsi&m=115507374832500&w=2
The patch has been updated to optimize the send path, per the discussions
in the initial posting.
Per discussions at the Storage Summit and at OLS, we are to use netlink for
async events from transports. Also per discussions, to avoid a netlink
protocol per transport, I've create a single NETLINK_SCSITRANSPORT protocol,
which can then be used by all transports.
This patch:
- Creates new files scsi_netlink.c and scsi_netlink.h, which contains the
single and shared definitions for the SCSI Transport. It is tied into the
base SCSI subsystem intialization.
Contains a single interface routine, scsi_send_transport_event(), for a
transport to send an event (via multicast to a protocol specific group).
- Creates a new scsi_netlink_fc.h file, which contains the FC netlink event
messages
- Adds 3 new routines to the fc transport:
fc_get_event_number() - to get a FC event #
fc_host_post_event() - to send a simple FC event (32 bits of data)
fc_host_post_vendor_event() - to send a Vendor unique event, with
arbitrary amounts of data.
Note: the separation of event number allows for a LLD to send a standard
event, followed by vendor-specific data for the event.
Note: This patch assumes 2 prior fc transport patches have been installed:
http://marc.theaimsgroup.com/?l=linux-scsi&m=115555807316329&w=2
http://marc.theaimsgroup.com/?l=linux-scsi&m=115581614930261&w=2
Sorry - next time I'll do something like making these individual
patches of the same posting when I know they'll be posted closely
together.
Signed-off-by: James Smart <James.Smart@emulex.com>
Tidy up configuration not to make SCSI always select NET
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
2006-08-19 01:30:09 +04:00
scsi_mod-$(CONFIG_SCSI_NETLINK) += scsi_netlink.o
2005-04-17 02:20:36 +04:00
scsi_mod-$(CONFIG_SYSCTL) += scsi_sysctl.o
scsi_mod-$(CONFIG_SCSI_PROC_FS) += scsi_proc.o
2017-04-26 23:47:57 +03:00
scsi_mod-$(CONFIG_BLK_DEBUG_FS) += scsi_debugfs.o
2015-01-08 09:43:42 +03:00
scsi_mod-y += scsi_trace.o scsi_logging.o
2011-02-11 02:06:54 +03:00
scsi_mod-$(CONFIG_PM) += scsi_pm.o
2015-08-27 15:16:57 +03:00
scsi_mod-$(CONFIG_SCSI_DH) += scsi_dh.o
2021-07-24 10:20:23 +03:00
scsi_mod-$(CONFIG_BLK_DEV_BSG) += scsi_bsg.o
2005-04-17 02:20:36 +04:00
2012-02-10 02:14:48 +04:00
hv_storvsc-y := storvsc_drv.o
2005-04-17 02:20:36 +04:00
sd_mod-objs := sd.o
2008-07-17 12:28:35 +04:00
sd_mod-$(CONFIG_BLK_DEV_INTEGRITY) += sd_dif.o
2016-10-18 09:40:34 +03:00
sd_mod-$(CONFIG_BLK_DEV_ZONED) += sd_zbc.o
2008-07-17 12:28:35 +04:00
2005-04-17 02:20:36 +04:00
sr_mod-objs := sr.o sr_ioctl.o sr_vendor.o
n c r 5 3 c 8 x x - f l a g s - $( CONFIG_SCSI_ZALON ) \
:= -DCONFIG_NCR53C8XX_PREFETCH -DSCSI_NCR_BIG_ENDIAN \
-DCONFIG_SCSI_NCR53C8XX_NO_WORD_TRANSFERS
CFLAGS_ncr53c8xx.o := $( ncr53c8xx-flags-y) $( ncr53c8xx-flags-m)
zalon7xx-objs := zalon.o ncr53c8xx.o
# Files generated that shall be removed upon make clean
2021-08-19 04:23:39 +03:00
clean-files := 53c700_d.h 53c700_u.h
2005-04-17 02:20:36 +04:00
2019-07-17 09:17:52 +03:00
$(obj)/53c700.o : $( obj ) /53c 700_d .h
2005-04-17 02:20:36 +04:00
2017-10-02 17:26:34 +03:00
$(obj)/scsi_sysfs.o : $( obj ) /scsi_devinfo_tbl .c
quiet_cmd_bflags = GEN $@
2018-04-18 02:35:09 +03:00
cmd_bflags = sed -n 's/.*define *BLIST_\([A-Z0-9_]*\) *.*/BLIST_FLAG_NAME(\1),/p' $< > $@
2017-10-02 17:26:34 +03:00
2021-08-19 04:23:39 +03:00
$(obj)/scsi_devinfo_tbl.c : include /scsi /scsi_devinfo .h FORCE
2017-10-02 17:26:34 +03:00
$( call if_changed,bflags)
2021-08-19 04:23:39 +03:00
targets += scsi_devinfo_tbl.c
2005-04-17 02:20:36 +04:00
# If you want to play with the firmware, uncomment
# GENERATE_FIRMWARE := 1
i f d e f G E N E R A T E _ F I R M W A R E
$(obj)/53c700_d.h : $( src ) /53c 700.scr $( src ) /script_asm .pl
$( PERL) -s $( src) /script_asm.pl -ncr7x0_family $@ $( @:_d.h= _u.h) < $<
e n d i f