Andy Ross dd33b37eff tests/sched/scheduler_api: samples/philosophers: Use SCHED_SCALABLE ... These two tests ask for lots of priority levels, more than the 32 maximum allowed by SCHED_MULTIQ (which is by design: if you have requirements like that DUMB or SCALABLE are better choices due to the RAM overhead of MULTIQ), so the build will fail on boards that defined MULTIQ as default. Don't let the platform choose the scheduler backend, ask for SCALABLE explicitly. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>		2018-07-03 17:09:15 -04:00
..
application_development
benchmarks
bluetooth
boards
booting/stub
compliance
crypto	tests: Cleanup converting int result to string	2018-06-29 11:53:59 -05:00
drivers	tests: fix struct initialization	2018-07-01 22:58:23 +02:00
include	tests: Cleanup converting int result to string	2018-06-29 11:53:59 -05:00
kernel	tests/sched/scheduler_api: samples/philosophers: Use SCHED_SCALABLE	2018-07-03 17:09:15 -04:00
lib
misc/test_build
net	net: config: Introduce a dedicated header for the library	2018-07-02 12:36:35 +03:00
posix
power
shell
subsys
unit
ztest
CMakeLists.txt
Kconfig	native_posix: Do not select COVERAGE by default	2018-07-03 08:36:06 -04:00