This website requires JavaScript.
Explore
Help
Register
Sign In
Mirrors_Framework
/
nuttx
Watch
1
Star
0
Fork
0
You've already forked nuttx
mirror of
https://github.com/apache/nuttx.git
synced
2026-05-14 11:28:22 +08:00
Code
Issues
Actions
Packages
Projects
Releases
Wiki
Activity
Files
e29b50e00a885ff616a2af2e3fc6bfb845e7b242
nuttx
/
sched
/
wqueue
T
History
Heesub Shin
8e94d8e7cc
Signal sent from work_signal() may interrupt the low priority worker thread that is already running. For example, the worker thread that is waiting for a semaphore could be woken up by the signal and break any synchronization assumption as a result. It also does not make any sense to send signal if it is already running and busy. This commit fixes it.
2016-11-06 08:00:12 -06:00
..
kwork_cancel.c
…
kwork_hpthread.c
Without lowsyslog() *llerr() is not useful. Eliminate and replace with *err().
2016-06-20 12:44:38 -06:00
kwork_inherit.c
…
kwork_lpthread.c
Without lowsyslog() *llerr() is not useful. Eliminate and replace with *err().
2016-06-20 12:44:38 -06:00
kwork_process.c
sched/: Review and correct some stylistic inconsistencies
2016-08-07 08:25:30 -06:00
kwork_queue.c
Signal sent from work_signal() may interrupt the low priority worker thread that is already running. For example, the worker thread that is waiting for a semaphore could be woken up by the signal and break any synchronization assumption as a result. It also does not make any sense to send signal if it is already running and busy. This commit fixes it.
2016-11-06 08:00:12 -06:00
kwork_signal.c
Signal sent from work_signal() may interrupt the low priority worker thread that is already running. For example, the worker thread that is waiting for a semaphore could be woken up by the signal and break any synchronization assumption as a result. It also does not make any sense to send signal if it is already running and busy. This commit fixes it.
2016-11-06 08:00:12 -06:00
Make.defs
…
wqueue.h
…