[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v4 00/16] basic vfio-ccw infrastructure
From: |
Cornelia Huck |
Subject: |
Re: [Qemu-devel] [PATCH v4 00/16] basic vfio-ccw infrastructure |
Date: |
Tue, 28 Mar 2017 15:31:52 +0200 |
On Tue, 28 Mar 2017 10:39:40 +0200
Christian Borntraeger <address@hidden> 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
- [Qemu-devel] [PATCH v4 13/16] vfio: ccw: introduce a finite state machine, (continued)
[Qemu-devel] [PATCH v4 15/16] vfio: ccw: introduce support for ccw0, Dong Jia Shi, 2017/03/16
[Qemu-devel] [PATCH v4 16/16] MAINTAINERS: Add vfio-ccw maintainers, Dong Jia Shi, 2017/03/16
Re: [Qemu-devel] [PATCH v4 00/16] basic vfio-ccw infrastructure, Cornelia Huck, 2017/03/28