Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272920AbTHEXWf (ORCPT ); Tue, 5 Aug 2003 19:22:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272947AbTHEXWd (ORCPT ); Tue, 5 Aug 2003 19:22:33 -0400 Received: from mail0.lsil.com ([147.145.40.20]:57522 "EHLO mail0.lsil.com") by vger.kernel.org with ESMTP id S272920AbTHEXWc (ORCPT ); Tue, 5 Aug 2003 19:22:32 -0400 Message-Id: <0E3FA95632D6D047BA649F95DAB60E570185F3FA@EXA-ATLANTA.se.lsil.com> From: "Mukker, Atul" To: "'Christoph Hellwig'" Cc: "'linux-kernel@vger.kernel.org'" , "'linux-scsi@vger.kernel.org'" , "'linux-megaraid-devel@dell.com'" Subject: RE: [ANNOUNCE] megaraid linux driver version 2.00.7 Date: Tue, 5 Aug 2003 18:09:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 607 Lines: 14 > + spin_lock_irqsave(adapter->host->host_lock, flags); But all kernels do not have this lock as part of the host structure. With 2.00.7, I have relapsed a patch which switches the lock to io_request_lock if kernel does not support per host lock. And not all kernels have the per host lock named as "host->host_lock", some simply have "host->lock" -Atul Mukker - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/