Thread (2 messages) flat view 2 messages, 1 author, 2016-02-14

RE: [PATCH V6 0/8] introduce Hyper-V VM Socket(hv_sock)

From: Dexuan Cui <decui@microsoft.com>
Date: 2016-02-14 05:30:20
Also in: lkml

From: devel [mailto:driverdev-devel-bounces@linuxdriverproject.org] On Behalf
Of Dexuan Cui
Sent: Tuesday, January 26, 2016 17:40
...
Dexuan Cui (8):
  Drivers: hv: vmbus: add a helper function to set a channel's pending
    send size
  Drivers: hv: vmbus: define the new offer type for Hyper-V socket
    (hvsock)
  Drivers: hv: vmbus: vmbus_sendpacket_ctl: hvsock: avoid unnecessary
    signaling
  Drivers: hv: vmbus: define a new VMBus message type for hvsock
  Drivers: hv: vmbus: add a hvsock flag in struct hv_driver
  Drivers: hv: vmbus: add a per-channel rescind callback
  Drivers: hv: vmbus: add an API vmbus_hvsock_device_unregister()
  hvsock: introduce Hyper-V Socket feature
Hi David,
Greg has accepted all my VMBus driver side's patches.
I'm going to post the net/hv_sock/ patch now.

I know I should rebase my patch to the net-next tree, but net-next hasn't
contained my VMBus driver side's patches, which are a prerequisite of my
net/hv_sock/ patch.

It looks I have to wait before you merge net-next with Greg's tree, or
with the mainline (after Greg pushes the changes to the mainline)?
If so, may I know when the next merge will be happening (so I don't need
to check net-next every day :-) ) ?

Thanks,
-- Dexuan
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help