[riot-notifications] [RIOT-OS/RIOT] cpu/fe310: don't call thread_yield when sched_active_thread is invalid (#12109)

Martine Lenders notifications at github.com
Mon Sep 16 12:36:54 CEST 2019

> **Disclaimer:** I am not a riscv expert, but I think it's pretty obvious that calling `thread_yield()` with an invalid `sched_active_thread` is a bad idea, unless you want to rely on the cpu not raising a trap/exception.

I would call myself even less of an expert, especially when it comes to cpu/board internals, so not sure why I was tagged. @kaspar030 @aabadie can one of you maybe test this? The fix looks fine to my limited understanding.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190916/f935acf9/attachment-0001.htm>

More information about the notifications mailing list