On Fri, Feb 01, 2019 at 04:19:41PM +0800, Stefan Hajnoczi wrote:
> On Tue, Jan 29, 2019 at 04:33:58PM +0100, Stefano Garzarella wrote:
> > Kindly ping :)
>
> Hi Stefano,
> It probably didn't get picked up due to the "RFC" (Request for
> Comments).
>
> I suggest rebasing, retesting, and resending to
On Tue, Jan 29, 2019 at 04:33:58PM +0100, Stefano Garzarella wrote:
> Kindly ping :)
Hi Stefano,
It probably didn't get picked up due to the "RFC" (Request for
Comments).
I suggest rebasing, retesting, and resending to be sure it will be
noticed and merged without conflicts.
Stefan
signature.a
Kindly ping :)
On Fri, Jan 4, 2019 at 3:34 PM Stefano Garzarella wrote:
>
> These patches try to handle the hot-unplug of vsock virtio transport device in
> a proper way.
>
> Maybe move the vsock_core_init()/vsock_core_exit() functions in the
> module_init
> and module_exit of vsock_virtio_trans
These patches try to handle the hot-unplug of vsock virtio transport device in
a proper way.
Maybe move the vsock_core_init()/vsock_core_exit() functions in the module_init
and module_exit of vsock_virtio_transport module can't be the best way, but the
architecture of vsock_core forces us to this
