Skip to content

marginalize HCIL a bit

Jeff Garzik linux-scsi 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest9 patches 2 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/9kill unused scsi_scan_single_target()drivers/scsi/scsi_scan.c include/scsi/scsi_host.h+0 -150 replies
2/9remove cpqfcTS driver, long uncompilable+0 -00 replies
3/9misc cleanupsdrivers/scsi/scsi.c include/scsi/scsi_device.h+4 -101 reply
4/9s/scsi_scan_target/spi_scan_target/drivers/scsi/scsi_scan.c drivers/scsi/scsi_transport_fc.c drivers/scsi/scsi_transport_sas.c +1 more+11 -110 replies
5/9split up __spi_scan_target()drivers/scsi/scsi_scan.c+19 -140 replies
6/9introduce sfoo_printk, sfoo_id, sfoo_channel helpersinclude/scsi/scsi_device.h include/scsi/scsi_host.h+26 -00 replies
7/9use {sdev,scmd,starget,shost}_printk in generic codedrivers/scsi/constants.c drivers/scsi/hosts.c drivers/scsi/scsi.c +11 more+88 -1280 replies
8/9use sfoo_printk() in driversdrivers/scsi/3w-9xxx.c drivers/scsi/3w-xxxx.c drivers/scsi/53c700.c +18 more+154 -1640 replies
9/9use scmd_id(), scmd_channel() throughout codedrivers/scsi/53c700.c drivers/scsi/NCR5380.c drivers/scsi/NCR53C9x.c +22 more+91 -890 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [scsi hcil 0/9] marginalize HCIL a bit

The following patches are in the 'submit9' branch of rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/scsilun-2.6.git

1     [SCSI] kill unused scsi_scan_single_target()
2     [SCSI] remove cpqfcTS driver, long uncompilable
3     [SCSI] misc cleanups
4     [SCSI] s/scsi_scan_target/spi_scan_target/
5     [SCSI] split up __spi_scan_target()
6     [SCSI] introduce sfoo_printk, sfoo_id, sfoo_channel helpers
7     [SCSI] use {sdev,scmd,starget,shost}_printk in generic code
8     [SCSI] use sfoo_printk() in drivers
9     [SCSI] use scmd_id(), scmd_channel() throughout code

Except for patch #2, which is too large to post, the above patches will follow this email.

If you are pulling the git repo, then you may branches submit0 (==Linus) through submit9 (==all patches). Each is cumulative: submit0 is empty. submit1 contains patch #1. submit2 contains patch #1 and #2. etc.

These patches are properly split up, and should be OK for upstream once 2.6.14 is released (any day now).