From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: Asynchronous scsi scanning Date: Thu, 17 May 2007 13:39:54 -0600 Message-ID: <20070517193953.GM10562@parisc-linux.org> References: <20070515172905.GJ10562@parisc-linux.org> <20070516025121.GK10562@parisc-linux.org> <20070517172023.GL10562@parisc-linux.org> <20070517182414.GA12170@infradead.org> <20070517185115.GA13207@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:47928 "EHLO mail.parisc-linux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754072AbXEQTj4 (ORCPT ); Thu, 17 May 2007 15:39:56 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Satyam Sharma Cc: Christoph Hellwig , Benjamin LaHaise , Simon Arlott , James Bottomley , Dave Jones , Linux Kernel Mailing List , linux-scsi@vger.kernel.org, kernel-packagers@vger.kernel.org, "Robert P. J. Day" On Fri, May 18, 2007 at 12:34:40AM +0530, Satyam Sharma wrote: > Hmmm, actually those other users could easily write and maintain > a 20-line patch that does the wait for async scans thing for them > using /proc/scsi/scsi in any case. How about the three users who're bothered by this extra module being built maintain a one-line patch to Kconfig and leave well enough alone?