From: James Bottomley <James.Bottomley@SteelEye.com>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PATCH] scsi merge for 2.6.13
Date: Mon, 12 Sep 2005 21:44:48 -0500 [thread overview]
Message-ID: <1126579489.4825.5.camel@mulgrave> (raw)
This should be the final round of changes before we close down into bug
fix mode. There will be a few extra driver updates in some of the -rc
stages (there's at least aacraid and zfcp still going through the
process).
The patch is available here [URL checked this time]
master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-for-linus-2.6.git
The short change log is:
adam radford:
o 3ware 9000: handle use_sg != 0 for emulated commands
Alan Stern:
o Fix module removal/device add race
o fix callers of scsi_remove_device() who already hold the scan muted
o add missing scan mutex to scsi_scan_target()
Andrew Vasquez:
o lpfc: use wwn_to_u64() transport helper
o qla2xxx: use wwn_to_u64() transport helper
o fc_transport: Generalize WWN to u64 interger conversions
Christoph Hellwig:
o SAS transport class
Douglas Gilbert:
o permit READ DEFECT DATA in block/scsi_ioctl
o sg: do not set VM_IO flag on mmap-ed pages
James Bottomley:
o Alter the scsi_add_device() API to conform to what users expect
o SAS transport class: fixup prototype of sas_host_setup
o core: fix leakage of scsi_cmnd's
o core: fix leakage of scsi_cmnd's
Mike Christie:
o set error value when failing commands in prep_fn
Neil Brown:
o fix possible deadlock in scsi_lib.c
Tejun Heo:
o scsi: Error handler description document
The diffstat is:
Documentation/scsi/00-INDEX | 2
Documentation/scsi/scsi_eh.txt | 479 ++++++++++++++++++++++
drivers/block/scsi_ioctl.c | 1
drivers/ieee1394/sbp2.c | 8
drivers/scsi/3w-9xxx.c | 30 +
drivers/scsi/Kconfig | 7
drivers/scsi/Makefile | 1
drivers/scsi/lpfc/lpfc_attr.c | 22 -
drivers/scsi/lpfc/lpfc_hbadisc.c | 7
drivers/scsi/lpfc/lpfc_hw.h | 17
drivers/scsi/lpfc/lpfc_init.c | 7
drivers/scsi/qla2xxx/qla_attr.c | 18
drivers/scsi/qla2xxx/qla_init.c | 4
drivers/scsi/scsi_lib.c | 138 ++++--
drivers/scsi/scsi_priv.h | 1
drivers/scsi/scsi_scan.c | 88 ++--
drivers/scsi/scsi_sysfs.c | 28 -
drivers/scsi/scsi_transport_sas.c | 820 ++++++++++++++++++++++++++++++++++++++
drivers/scsi/sg.c | 4
include/scsi/scsi_device.h | 4
include/scsi/scsi_transport_fc.h | 8
include/scsi/scsi_transport_sas.h | 100 ++++
22 files changed, 1648 insertions(+), 146 deletions(-)
James
next reply other threads:[~2005-09-13 2:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 2:44 James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-07 0:37 [GIT PATCH] SCSI merge for 2.6.13 James Bottomley
2005-09-07 17:47 ` Patrick Mansfield
2005-09-07 18:14 ` James Bottomley
2005-09-07 19:35 ` Jens Axboe
2005-09-08 0:31 ` Linus Torvalds
2005-09-08 0:40 ` James Bottomley
2005-09-08 0:41 ` Linus Torvalds
2005-09-08 0:49 ` Linus Torvalds
2005-09-08 0:56 ` James Bottomley
2005-09-08 0:59 ` Andrew Morton
2005-09-08 0:53 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1126579489.4825.5.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox