summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2015-04-20 15:25:19 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2015-04-20 15:25:19 -0700
commitb153f1d37a7d469501482bb3b38f398d4e778616 (patch)
treeecde7c3c677b04c3f1413637fd42f61870c6bee3 /scripts
parentbf2ae5d337cd09dfee3041364a36c5214cc7faf9 (diff)
parent56cbd0ccc1b508de19561211d7ab9e1c77e6b384 (diff)
downloadlinux-b153f1d37a7d469501482bb3b38f398d4e778616.tar.bz2
Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
Pull SCSI fixes from James Bottomley: "I'd like to say these were a set of regressions for the recent merge window code. Unfortunately, they all predate the merge window code (stable cc'd). There are two fixes for data integrity (mostly only showing up on module removal), an mvsas crash with expander attached SATA devices which goes back to the dawn of the driver but is only just being picked up as sas expanders become a standard item in low end server hardware, an am53c974 one because the interrupt data isn't fully initialised before the line is and a megaraid_sas one because it uses smp_processor_id() to select MSI-X queues and that now triggers a WARN_ON()" * tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi: mvsas: fix panic on expander attached SATA devices am53c974: Fix crash during modprobe megaraid_sas: use raw_smp_processor_id() sd: Fix missing ATO tag check sd: Unregister integrity profile
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions