Kedar Sovani 700976f709 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:18:34 +05:30
..
include	Merge branch 'feature/mbedtls_mem_alloc_options' into 'master'	2018-09-25 08:24:29 +08:00
esp_bignum.c	mbedtls: Fix Z->s in mbedtls_mpi_exp_mod()	2019-06-26 14:20:30 +08:00
esp_hardware.c	esp32: Add esp_fill_random() function	2018-09-03 04:39:45 +00:00
esp_mem.c	mbedtls: configurable options for controlling dynamic memory allocations	2018-09-24 11:17:48 +05:30
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	gcc8_newlib3: Compilation warnings and errors not specific to newlib v3	2018-07-09 13:22:24 +03:00
net_sockets.c	Remove check for would_block in mbedtls	2019-10-18 14:18:34 +05:30