[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 3/7] virtio-pmem: sync linux headers
From: |
Pankaj Gupta |
Subject: |
Re: [Qemu-devel] [PATCH v2 3/7] virtio-pmem: sync linux headers |
Date: |
Tue, 2 Jul 2019 13:21:47 -0400 (EDT) |
> > > >
> > > > >
> > > > > On Wed, 19 Jun 2019 15:19:03 +0530
> > > > > Pankaj Gupta <address@hidden> wrote:
> > > > >
> > > > > > Sync linux headers for virtio pmem.
> > > > > >
> > > > > > Signed-off-by: Pankaj Gupta <address@hidden>
> > > > > > ---
> > > > > > include/standard-headers/linux/virtio_ids.h | 1 +
> > > > > > include/standard-headers/linux/virtio_pmem.h | 35
> > > > > > ++++++++++++++++++++++++++++
> > > > > > 2 files changed, 36 insertions(+)
> > > > > > create mode 100644 include/standard-headers/linux/virtio_pmem.h
> > > > >
> > > > > That's not yet upstream, right?
> > > >
> > > > right.
> > > >
> > > > >
> > > > > If so, I fear this feature won't make 4.1, as the merge window for
> > > > > Linux only opens in one or two weeks :(
> > > >
> > > > Looks so. Its lined up for 5.3 merge window.
> > >
> > > In which tree is it?
> >
> > Patches are in Dan's tree:
> > https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git/log/?h=libnvdimm-pending
> >
> > Thanks,
> > Pankaj
>
> Hmm ok, but that isn't part of linux-next. Do you know why?
Dan suggested to first apply in libnvdimm-pending tree to check for any zero
day test bot
warnings and then apply in linux-next. So, I think next step is to merge in
linux-next.
Thanks,
Pankaj
>
> > >
> > > > Waiting for the kernel patch series to be merged and send an updated
> > > > version
> > > > of qemu series with review suggestion if any :)
> > > >
> > > > Thanks,
> > > > Pankaj
> > > >
> > > > >
> > >
>
[Qemu-devel] [PULL 05/22] virtio-pmem: add virtio device, Michael S. Tsirkin, 2019/07/02
[Qemu-devel] [PULL 08/22] virtio-pci: Proxy for virtio-pmem, Michael S. Tsirkin, 2019/07/02