From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] remove scsi_assign_lock Date: Fri, 13 Jan 2006 19:44:22 +0100 Message-ID: <20060113184422.GA4605@lst.de> References: <20060113182543.GA4148@lst.de> <20060113183736.GQ19769@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from verein.lst.de ([213.95.11.210]:7903 "EHLO mail.lst.de") by vger.kernel.org with ESMTP id S1422816AbWAMSoZ (ORCPT ); Fri, 13 Jan 2006 13:44:25 -0500 Content-Disposition: inline In-Reply-To: <20060113183736.GQ19769@parisc-linux.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Matthew Wilcox Cc: Christoph Hellwig , jejb@steeleye.com, linux-scsi@vger.kernel.org On Fri, Jan 13, 2006 at 11:37:36AM -0700, Matthew Wilcox wrote: > On Fri, Jan 13, 2006 at 07:25:43PM +0100, Christoph Hellwig wrote: > > We finally fixed all drivers to not require this hack, so let's get rid > > of it before people reintroduce uses (vendor drivers seem to be very > > eager to use it for no obvious reason) > > Although of course they'll now just assign to host_lock direectly. > Presumably you intend to remove that in the near future, but didn't do > that now because it would introduce too much code churn? yes.