Gregory Nutt ccdc11d8ff Fix typo in variable naming. g_cpu_irqset should be g_cpu_irqlock.		2016-11-17 06:37:24 -06:00
..
clock	Correct time initialization for the case where time is initialized from settings in the .config file. The correct range for month (tm_mon) internally is 0-11, not 1-12 as it is in the .config file.	2016-10-27 08:36:24 -06:00
environ	sched/: Review and correct some stylistic inconsistencies	2016-08-07 08:25:30 -06:00
errno	Remove some empty file section section header comments	2016-02-17 18:05:03 -06:00
group	sched: Disable priority inheritance on all semaphores used for signaling	2016-11-03 12:42:02 -06:00
init	Trivia fix to typo in comment	2016-10-26 12:29:36 -06:00
irq	Fix typo in variable naming. g_cpu_irqset should be g_cpu_irqlock.	2016-11-17 06:37:24 -06:00
module	Without lowsyslog() *llinfo() is not useful. Eliminate and replace with *info().	2016-06-20 11:59:15 -06:00
mqueue	Correct a comment	2016-09-15 13:10:42 -06:00
paging	Without lowsyslog() *llinfo() is not useful. Eliminate and replace with *info().	2016-06-20 11:59:15 -06:00
pthread	Update TODO. Provide do-nothing stubs for mutex attribute interfaces if features not enabled. pthread_cond includes a signaling semaphore and should call sem_setprotocol.	2016-11-05 11:06:52 -06:00
sched	sched/: Move fields related to parent/child task relationship out of TCB into group structure.	2016-09-06 08:28:31 -06:00
semaphore	sem_wait() and sem_trywait() no longer modify the errno value UNLESS an error occurs. This allows these functions to be used internallly without clobbering the errno value.	2016-11-09 07:01:49 -06:00
signal	Explicitly initialize the group tg_exitsem with sem_init(). The existing logic worked because the correct initialization value is all zero, but it is better to initialize the semaphore explicitly. Noted by Jouko Holopainen.	2016-08-10 07:38:07 -06:00
task	sched/pthread and task: When a pthread is started, there is a small bit of logic that will run on the thread of execution of the new pthread. In the case where the new pthread has a lower priority than the parent thread, then this could cause both the parent thread and the new pthread to be blocked at the priority of the lower priority pthread (assuming that CONFIG_PRIORITY_INHERITANCE is not selected).	2016-10-01 11:38:22 -06:00
timer	sched/: Review and correct some stylistic inconsistencies	2016-08-07 08:32:11 -06:00
wdog	sched/: Review and correct some stylistic inconsistencies	2016-08-07 08:25:30 -06:00
wqueue	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
.gitignore	…
Kconfig	Update some Kconfig comments	2016-11-06 09:06:37 -06:00
Makefile	TLS: Simplify	2016-03-11 07:17:32 -06:00