forked from nuttx/nuttx-update
tcp_close_disconnect: don't nullify sndcb
It isn't necessary and I plan to use the value later in the close processing.
This commit is contained in:
parent
8472430f22
commit
326a8ef0a2
1 changed files with 0 additions and 10 deletions
|
@ -262,16 +262,6 @@ static inline int tcp_close_disconnect(FAR struct socket *psock)
|
|||
}
|
||||
#endif
|
||||
|
||||
#ifdef CONFIG_NET_TCP_WRITE_BUFFERS
|
||||
/* If we have a semi-permanent write buffer callback in place, then
|
||||
* is needs to be be nullified.
|
||||
*
|
||||
* Note: the callback will be freed by tcp_free.
|
||||
*/
|
||||
|
||||
psock->s_sndcb = NULL;
|
||||
#endif
|
||||
|
||||
/* Check for the case where the host beat us and disconnected first */
|
||||
|
||||
if (conn->tcpstateflags == TCP_ESTABLISHED &&
|
||||
|
|
Loading…
Reference in a new issue