diff options
author | 2018-12-19 10:58:35 -0500 | |
---|---|---|
committer | 2019-01-02 12:05:16 -0500 | |
commit | 3d433ad812baad45fa697f1af45a651147360712 (patch) | |
tree | 63aa13fe967384a1cb8eca1c2bcd1616c936f339 /net/bluetooth/hci_request.c | |
parent | xprtrdma: Replace rpcrdma_receive_wq with a per-xprt workqueue (diff) | |
download | wireguard-linux-3d433ad812baad45fa697f1af45a651147360712.tar.xz wireguard-linux-3d433ad812baad45fa697f1af45a651147360712.zip |
xprtrdma: No qp_event disconnect
After thinking about this more, and auditing other kernel ULP imple-
mentations, I believe that a DISCONNECT cm_event will occur after a
fatal QP event. If that's the case, there's no need for an explicit
disconnect in the QP event handler.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'net/bluetooth/hci_request.c')
0 files changed, 0 insertions, 0 deletions