Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760608AbXEOXtv (ORCPT ); Tue, 15 May 2007 19:49:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757558AbXEOXtn (ORCPT ); Tue, 15 May 2007 19:49:43 -0400 Received: from ug-out-1314.google.com ([66.249.92.169]:36397 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757391AbXEOXtl (ORCPT ); Tue, 15 May 2007 19:49:41 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=V/WkJXFwliVzkBF95I93AScqR1GVEumLyRSvqbWfk9xYf/BU3kcInmhxTRIF+dKlWIo9nPQfRL8v2mdBxHCC+S8ZaqNA076vNHrJi6iPEnMFfHCeFZkvbcGV7X7a57aSP7Pxl8lRdqgkXAitBswuiaT/wyS1QmDcMYRgJbu+KQQ= Message-ID: Date: Wed, 16 May 2007 05:19:40 +0530 From: "Satyam Sharma" To: "Arjan van de Ven" Subject: Re: Asynchronous scsi scanning Cc: "Matthew Wilcox" , "Simon Arlott" , "James Bottomley" , "Dave Jones" , "Linux Kernel Mailing List" , linux-scsi@vger.kernel.org, kernel-packagers@vger.kernel.org, "Robert P. J. Day" In-Reply-To: <464A4222.4000208@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1179073116.3723.45.camel@mulgrave.il.steeleye.com> <1179153096.3703.23.camel@mulgrave.il.steeleye.com> <17841.simon.1179228389@5ec7c279.invalid> <20070515120228.GI10562@parisc-linux.org> <4649E03A.1090004@simon.arlott.org.uk> <20070515172905.GJ10562@parisc-linux.org> <464A4222.4000208@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1114 Lines: 27 On 5/16/07, Arjan van de Ven wrote: > Satyam Sharma wrote: > >> > >semantics of it (read-only? read-write? write-only? > > > > Well, it _has_ to be write, don't really care if it's read-write or > > write-only. I would still prefer read-write, but we can go ahead with > > write-only too. It doesn't really matter, does it? > > just to be devils advocate... > it should be a read that returns when done, Heh, yeah. We just need to trigger that scsi_complete_async_scans() after all ... might as well abuse all intuition on the user's behalf :-) > and that can be polled Gaah! :-) But seriously, though, this sysfs attribute can be implemented _any which way_. Better for us if we do it the simplest way (and which taxes the user's intuition the least). Just that Matthew asked so many questions so I thought I might as well answer them :-) - 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/