On 2/9/22 04:13, Paul Gofman wrote:
Signed-off-by: Paul Gofman pgofman@codeweavers.com
The old winsock implementation was printing warnings for any error status from socket operation. That was handy for debugging. Without that pretty much any problem analysis involving tracing network operations starts from adding such logs.
I don't object to this in general, but can we at least avoid warning on EWOULDBLOCK / STATUS_DEVICE_NOT_READY where relevant?