mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-01 17:30:42 +00:00
There could be cases where the destroy callback needs more fine-grained control of step ordering than "1. destroy, 2. put back to free FIFO". One case could be when the the pool needs to be protected by a microkernel mutex or semaphore. In such a case the putting back to the FIFO may need to happen before a custom action in the destroy callback. Making the destroy callback responsible for returning to the free FIFO gives full flexibility regarding the order of the cleanup actions. Change-Id: Ib9532d1dd70e0a2042af54ebd3e40a853dd42d33 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> |
||
---|---|---|
.. | ||
buf.h | ||
net_buf.h | ||
net_core.h | ||
net_ip.h | ||
net_socket.h | ||
tinydtls.h |