Kedar Sovani 8f048ffddc Remove check for would_block in mbedtls ... Basically, in the portability layer, it is checked if the socket is NON-block, and if not, then even the EAGAIN and EWOULDBLOCK errors are diverted to a RECV error. This causes a problem for sockets with receive timeouts set. When such a timeout is set, the condition for NON_BLOCK isn't met and hence a hard error is returned. Searching for EAGAIN and EWOULDBLOCK in lwip returns only 3 results (accept, recvfrom, close) and all of them look to be genuine cases for EWOULDBLOCK. So removing this check to make receive timeout with TLS work.		2019-10-18 14:21:35 +05:30
..
include	NimBLE: Port NimBLE stack to IDF Release v3.3 (Backport v3.3)	2019-10-18 13:23:24 +08:00
esp_bignum.c	mbedtls: Fix Z->s in mbedtls_mpi_exp_mod()	2019-06-26 14:19:40 +08:00
esp_hardware.c	mbedtls: import mbedtls project w/o modification	2018-11-27 13:59:26 +08:00
esp_mem.c	mbedtls: import mbedtls project w/o modification	2018-11-27 13:59:26 +08:00
esp_sha1.c	mbedtls: update usage of deprecated mbedtls_shaX APIs	2018-05-09 23:15:28 +08:00
esp_sha256.c	mbedtls: update usage of deprecated mbedtls_shaX APIs	2018-05-09 23:15:28 +08:00
esp_sha512.c	mbedtls: update usage of deprecated mbedtls_shaX APIs	2018-05-09 23:15:28 +08:00
mbedtls_debug.c	mbedtls: import mbedtls project w/o modification	2018-11-27 13:59:26 +08:00
net_sockets.c	Remove check for would_block in mbedtls	2019-10-18 14:21:35 +05:30