|
From: | Simon Goldschmidt |
Subject: | [lwip-devel] [patch #9534] freertos: misc fixes, core locking check support. |
Date: | Sat, 6 Jan 2018 08:25:12 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 |
Update of patch #9534 (project lwip): Open/Closed: Open => Closed _______________________________________________________ Follow-up Comment #4: Ok, so since we have a preprocessor check that INCLUDE_vTaskDelay is enabled, we should not need the loop. Maybe there's a return value to check for in the futuer. I'd rather go the safe way and check for "OK" instead of retrying for all possible erors. > was wondering if esp-open-rtos should follow that approach? It helps to keep the code cleaner and keep compile times low (less headers included). You might be able to save some bytes in the generated code though when doing it your way. You'd have to check that... _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/patch/?9534> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |