From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boaz Harrosh Subject: Re: [PATCH 1/2] RFC: Proposal for BSG Interface Date: Thu, 18 Mar 2010 14:55:36 +0200 Message-ID: <4BA222C8.80507@panasas.com> References: <20100317180557.GA25841@serverengines.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from daytona.panasas.com ([67.152.220.89]:9187 "EHLO daytona.int.panasas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753152Ab0CRMzk (ORCPT ); Thu, 18 Mar 2010 08:55:40 -0400 In-Reply-To: <20100317180557.GA25841@serverengines.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: open-iscsi@googlegroups.com Cc: Jayamohan Kallickal , linux-scsi@vger.kernel.org, James.Bottomley@suse.de, michaelc@cs.wisc.edu On 03/17/2010 08:06 PM, Jayamohan Kallickal wrote: > This patch contains the bsg interface based on > the bsg interface in FC. > What? where? who? how? why? w*\? ... You are proposing a new Kernel ABI/API here right. I think it is not acceptable without a detailed documentation, including every little bit. Nothing missing. If lots of it is already written for FC then grate most of your job is done. But for us mortals please put some text on an introductory message. I use iscsi everyday for 4 years, your mail should answer the question: "what am I missing?" > Developed and submitted earlier by James Smart. > > Signed-off-by: James Smart > Signed-off-by: Jayamohan Kallickal Boaz