On Tue, Jul 02, 2019 at 04:56:05PM +0100, Peter Maydell wrote: > On Tue, 2 Jul 2019 at 16:06, Michael S. Tsirkin <m...@redhat.com> wrote: > > > > The following changes since commit 7fec76a02267598a4e437ddfdaeaeb6de09b92f3: > > > > Merge remote-tracking branch > > 'remotes/maxreitz/tags/pull-block-2019-06-24' into staging (2019-07-01 > > 11:28:28 +0100) > > > > are available in the Git repository at: > > > > git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream > > > > for you to fetch changes up to a360cd11de5ae59db55e128fd209290c777eb177: > > > > docs: avoid vhost-user-net specifics in multiqueue section (2019-07-01 > > 10:39:35 -0400) > > > > ---------------------------------------------------------------- > > virtio, pc, pci: features, fixes, cleanups > > > > virtio-pmem support. > > libvhost user mq support. > > A bunch of fixes all over the place. > > > > Signed-off-by: Michael S. Tsirkin <m...@redhat.com> > > > > > Pankaj Gupta (3): > > virtio-pmem: sync linux headers > > Hi. This header sync doesn't look like it was a proper > sync made with the update-headers script against some > upstream kernel -- at least the commit message doesn't > say what the sync was against and the fact that it only > changes the virtio-pmem headers looks suspicious. > > Can you respin with a proper header sync against upstream > mainline, please? > > thanks > -- PMM
This isn't from mainline. We have a bit of a deadlock with linux merge window opening soon. I think it's reasonable temporarily and then before release either virtio-pmem gets there or I will revert it and drop the header. Updated the commit and re-pushed. But if you disagree pls let me know. -- MST
