From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cornelia Huck Subject: Re: [PATCH v4 00/16] basic vfio-ccw infrastructure Date: Tue, 28 Mar 2017 15:31:52 +0200 Message-ID: <20170328153152.16ddb794.cornelia.huck@de.ibm.com> References: <20170317031743.40128-1-bjsdjshi@linux.vnet.ibm.com> <20170328102016.4926f21d.cornelia.huck@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Dong Jia Shi , kvm@vger.kernel.org, linux-s390@vger.kernel.org, qemu-devel@nongnu.org, renxiaof@linux.vnet.ibm.com, agraf@suse.com, alex.williamson@redhat.com, pmorel@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com, Martin Schwidefsky , Paolo Bonzini To: Christian Borntraeger Return-path: Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:35246 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753621AbdC1NcN (ORCPT ); Tue, 28 Mar 2017 09:32:13 -0400 Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2SDNwL2083530 for ; Tue, 28 Mar 2017 09:32:02 -0400 Received: from e06smtp12.uk.ibm.com (e06smtp12.uk.ibm.com [195.75.94.108]) by mx0a-001b2d01.pphosted.com with ESMTP id 29frcchukr-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 28 Mar 2017 09:32:01 -0400 Received: from localhost by e06smtp12.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 28 Mar 2017 14:31:59 +0100 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Tue, 28 Mar 2017 10:39:40 +0200 Christian Borntraeger wrote: > On 03/28/2017 10:20 AM, Cornelia Huck wrote: > > Patch set looks good to me, and I think we should target it for the > > next merge window (the interface looks fine, and we can iron out any > > other things later.) > > > > Question: Which tree should this go through? Vfio or kvm/s390? > > Reading todays MAINTAINERS file this would go via Martins tree, after the last > patch it will be separate. I can certainly carry that via the kvms390 tree, > but Alex is certainly the final maintainer. > So what about having a new repository under > https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/ > e.g. vfio.git that will then queue the patches for Alex to take? Whatever we decide: Patches with collected acks pushed out to https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git vfio-ccw-v0