Andy Ross 8daafd4fba kernel: Final spin in !MULTITHREADING should be locked ... Now that we call main() with interrupts enabled in !MULTITHREADING, we need to disable them again for the final fallback "loop-forever because user code returned" state. Otherwise some architectures will toss interrupts into a context where we obviously aren't prepared. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>		2018-08-30 13:29:09 -04:00
..
include	sched: Properly account for timeslicing in tickless mode	2018-08-29 10:01:41 -04:00
alert.c
atomic_c.c
CMakeLists.txt
compiler_stack_protect.c
device.c
errno.c
idle.c
init.c	kernel: Final spin in !MULTITHREADING should be locked	2018-08-30 13:29:09 -04:00
int_latency_bench.c
Kconfig
Kconfig.power_mgmt	doc: fix kconfig misspellings	2018-08-28 13:58:46 -04:00
mailbox.c
mem_domain.c
mem_slab.c
mempool.c
msg_q.c
mutex.c
pipes.c	kernel: pipes: fix k_pipe_block_put() when not enough space	2018-08-29 15:57:28 -04:00
poll.c	kernel: k_poll: Introduce separate status for cancelled events	2018-08-30 09:28:29 -04:00
queue.c	kernel: k_poll: Introduce separate status for cancelled events	2018-08-30 09:28:29 -04:00
sched.c	sched: Properly account for timeslicing in tickless mode	2018-08-29 10:01:41 -04:00
sem.c
smp.c
stack.c
sys_clock.c	kernel: Remove unused variable	2018-08-26 19:39:52 -07:00
system_work_q.c
thread_abort.c
thread.c
timer.c
userspace_handler.c
userspace.c
version.c
work_q.c