doc: net: Remove obsolete note about sockets thread-safety status
The socket API was updated with mutex protection, however this was not reflected in the documentation. Remove the obsolete note on the thread-safety status of the socket API, to prevent confusion. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
This commit is contained in:
parent
10232b536e
commit
7abc68d432
1 changed files with 0 additions and 5 deletions
|
@ -146,11 +146,6 @@ Secure sockets offer the following options for socket management:
|
||||||
API Reference
|
API Reference
|
||||||
*************
|
*************
|
||||||
|
|
||||||
Note that current socket API implementation is not thread safe and caller
|
|
||||||
should not do socket operations to same socket from multiple threads unless
|
|
||||||
protected by a mutex, semaphore or similar.
|
|
||||||
|
|
||||||
|
|
||||||
BSD Sockets
|
BSD Sockets
|
||||||
===========
|
===========
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue