Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4def7fa11208f779f22e6ba7344370b0220d3350
Commit:     4def7fa11208f779f22e6ba7344370b0220d3350
Parent:     144ff8bf0d84a81806bfb5979b0a6b176b1fcace
Author:     Salyzyn, Mark <[EMAIL PROTECTED]>
AuthorDate: Fri Apr 13 08:35:25 2007 -0400
Committer:  James Bottomley <[EMAIL PROTECTED]>
CommitDate: Tue Apr 17 18:02:22 2007 -0400

    [SCSI] aacraid: fix aacraid not finding device
    
    Thanks for the help from Steve Fox and Duane Cox investigating this
    issue, I'd like to report that we found the problem. The issue is with
    the patch Steve Fox isolated below, by not accommodating older adapters
    properly and issuing a command they do not support when retrieving
    storage parameters about the arrays. This simple patch resolves the
    problem (and more accurately mimics the logic of the original code
    before the patch).
    
    Signed-off-by: Mark Salyzyn <[EMAIL PROTECTED]>
    Signed-off-by: James Bottomley <[EMAIL PROTECTED]>
---
 drivers/scsi/aacraid/aachba.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/drivers/scsi/aacraid/aachba.c b/drivers/scsi/aacraid/aachba.c
index 31ac9f5..1e82c69 100644
--- a/drivers/scsi/aacraid/aachba.c
+++ b/drivers/scsi/aacraid/aachba.c
@@ -503,8 +503,7 @@ static int _aac_probe_container1(void * context, struct fib 
* fibptr)
        dresp = (struct aac_mount *) fib_data(fibptr);
        dresp->mnt[0].capacityhigh = 0;
        if ((le32_to_cpu(dresp->status) != ST_OK) ||
-           ((le32_to_cpu(dresp->mnt[0].vol) != CT_NONE) &&
-            (le32_to_cpu(dresp->mnt[0].state) == FSCS_HIDDEN)))
+           (le32_to_cpu(dresp->mnt[0].vol) != CT_NONE))
                return _aac_probe_container2(context, fibptr);
        scsicmd = (struct scsi_cmnd *) context;
        scsicmd->SCp.phase = AAC_OWNER_MIDLEVEL;
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to