Kaspar Schleiser 622d473eb3 core: msg: yield after queueing of a message if REPLY_BLOCKED ... When setting the running task reply_blocked, it is implicitly removed from the runqueue. But if queueing of a msg is actually successful, the thread exits msg_send without yielding, continuing to run even if it's not supposed to. Nice example of why multiple function exit points lead to weird errors...		2014-02-13 11:33:18 +01:00
..
include	Portable definition of function attributes	2014-02-12 14:58:59 +01:00
bitarithm.c	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
cib.c	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
clist.c	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
doc.txt	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
hwtimer.c	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
kernel_init.c	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
lifo.c	refine DEVELHELP section	2013-12-20 11:51:52 +01:00
Makefile	removed redundant include pathes from Makefiles	2014-01-05 16:11:08 +01:00
msg.c	core: msg: yield after queueing of a message if REPLY_BLOCKED	2014-02-13 11:33:18 +01:00
mutex.c	update Kaspar's email address	2014-01-28 11:53:19 +01:00
oneway_malloc.c	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
queue.c	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
sched.c	remove trailing whitespace and newlines	2014-02-11 18:45:06 +01:00
thread.c	update Kaspar's email address	2014-01-28 11:53:19 +01:00