diff options
| author |   David S. Miller <davem@davemloft.net> | 2019-02-03 11:06:25 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-02-03 11:06:25 -0800 |
| commit | 2348bb3117e1c88fd7799cd751200eda84b55c23 (patch) | |
| tree | e06307c9f6e757d2263f5a4584054a8f7b338fda /drivers/net/ethernet/broadcom/bcmsysport.c | |
| parent | Revert "net: phy: marvell: avoid pause mode on SGMII-to-Copper for 88e151x" (diff) | |
| parent | vsock/virtio: reset connected sockets on device removal (diff) | |
| download | linux-dev-2348bb3117e1c88fd7799cd751200eda84b55c23.tar.xz linux-dev-2348bb3117e1c88fd7799cd751200eda84b55c23.zip | |
Merge branch 'vsock-virtio-hot-unplug'
Stefano Garzarella says:
====================
vsock/virtio: fix issues on device hot-unplug
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 approach for now.
The vsock_core proto_ops expect a valid pointer to the transport device, so we
can't call vsock_core_exit() until there are open sockets.
v2 -> v3:
- Rebased on master
v1 -> v2:
- Fixed commit message of patch 1.
- Added Reviewed-by, Acked-by tags by Stefan
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/broadcom/bcmsysport.c')
0 files changed, 0 insertions, 0 deletions