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

kenrabold notifications at github.com
Thu Sep 5 20:03:57 CEST 2019


I see what you are changing here and agree that thread_yield() should not be called cpu_switch_context_exit(). However, there is something else going on with the context changing code now because thread tests that were passing previously (eg. thread_msg_block_race, thread_race, etc...) are now not working. This PR is fine by me to address the immediate issue raised, but there is still a problem that needs fixing. I'm just not sure what that is at the moment.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/12109#issuecomment-528504900
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190905/110a8d72/attachment.htm>


More information about the notifications mailing list