Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753603AbaFMQl0 (ORCPT ); Fri, 13 Jun 2014 12:41:26 -0400 Received: from verein.lst.de ([213.95.11.211]:48132 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753339AbaFMQlY (ORCPT ); Fri, 13 Jun 2014 12:41:24 -0400 Date: Fri, 13 Jun 2014 18:41:18 +0200 From: Christoph Hellwig To: James Bottomley Cc: Christoph Hellwig , "Nicholas A. Bellinger" , Linus Torvalds , target-devel , linux-scsi , LKML , Stephen Rothwell , Paolo Bonzini , Quinn Tran , "Michael S. Tsirkin" , Rusty Russell Subject: Re: [GIT PULL] target updates for v3.16-rc1 Message-ID: <20140613164118.GA17282@lst.de> References: <1402607116.18202.46.camel@haakon3.risingtidesystems.com> <20140613133901.GC7371@lst.de> <1402672861.2224.11.camel@dabdike.int.hansenpartnership.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1402672861.2224.11.camel@dabdike.int.hansenpartnership.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 13, 2014 at 08:21:01AM -0700, James Bottomley wrote: > We've been ineffectively trying to split them between target and > initiator, since it's effectively both. Now that we seem to have a > workable process, why don't we just take everything (target scsi-queue > and vhost) through the SCSI tree, that way we don't get into these > problems in future. virtio-scsi has nothing to do with the target. I also think sending target updates through the scsi tree doesn't seem very useful, as there's is no shared code to start with. -- 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/