summaryrefslogtreecommitdiffstats
path: root/drivers/message/fusion/mptsas.c
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2006-01-30 19:00:43 +0100
committerJames Bottomley <jejb@mulgrave.(none)>2006-01-31 21:40:01 +0100
commit23f236ed2748fca0bcba304f4f9e3eacda51e91c (patch)
tree694b1c45f7b215b366bb0935e958012ca46040fa /drivers/message/fusion/mptsas.c
parent[SCSI] fusion: add task managment response code info (diff)
downloadlinux-23f236ed2748fca0bcba304f4f9e3eacda51e91c.tar.xz
linux-23f236ed2748fca0bcba304f4f9e3eacda51e91c.zip
[SCSI] mptsas: don't complain on bogus slave_alloc calls
When people use the userspace scanning facilities on SAS hardware the LLDD gets bogus slave_alloc calls. Just fail those gracefully instead of printing a warning in mptsas and another one in the midlayer. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to '')
-rw-r--r--drivers/message/fusion/mptsas.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/drivers/message/fusion/mptsas.c b/drivers/message/fusion/mptsas.c
index 90660bfa148c..2512d0e6155e 100644
--- a/drivers/message/fusion/mptsas.c
+++ b/drivers/message/fusion/mptsas.c
@@ -304,9 +304,8 @@ mptsas_slave_alloc(struct scsi_device *sdev)
}
mutex_unlock(&hd->ioc->sas_topology_mutex);
- printk("No matching SAS device found!!\n");
kfree(vdev);
- return -ENODEV;
+ return -ENXIO;
out:
vtarget->ioc_id = vdev->ioc_id;