advansys: Remove cmd_per_lun setting

Ancient, and pretty much obsolete by now.

Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: James Bottomley <JBottomley@Odin.com>

diff --git a/drivers/scsi/advansys.c b/drivers/scsi/advansys.c
index 474393e1ad5a5e80190c807bfec8460f5647ab1c..3408f14094441c96496dda409d59a3112efd3742 100644 (file)
--- a/drivers/scsi/advansys.c
+++ b/drivers/scsi/advansys.c
@@ -11211,24 +11211,6 @@ static int advansys_board_found(struct Scsi_Host *shost, unsigned int iop,
                goto err_free_dma;
        }
 
-       /*
-        * Following v1.3.89, 'cmd_per_lun' is no longer needed
-        * and should be set to zero.
-        *
-        * But because of a bug introduced in v1.3.89 if the driver is
-        * compiled as a module and 'cmd_per_lun' is zero, the Mid-Level
-        * SCSI function 'allocate_device' will panic. To allow the driver
-        * to work as a module in these kernels set 'cmd_per_lun' to 1.
-        *
-        * Note: This is wrong.  cmd_per_lun should be set to the depth
-        * you want on untagged devices always.
-        #ifdef MODULE
-        */
-       shost->cmd_per_lun = 1;
-/* #else
-            shost->cmd_per_lun = 0;
-#endif */
-
        /*
         * Set the maximum number of scatter-gather elements the
         * adapter can handle.