[riot-notifications] [RIOT-OS/RIOT] core/mutex: Add mutex_cancel (#15442)

chrysn notifications at github.com
Sun Nov 15 13:26:03 CET 2020


I've just only read through this being pinged -- what I don't quite understand from a first look at this is: Why does this need something changed around mutexes? Given that we have the mechanism of waiting for thread flags, can't a function like "lock this mutex or time out" just be implemented using `thread_flags_wait_one(THREAD_FLAG_MUTEX_READY | THREAD_FLAG_TIMEOUT)`?

(And I too see trouble in making a function that previously worked unconditionally suddenly fallible, but I may still lack parts of the big picture).

-- 
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/15442#issuecomment-727561907
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20201115/dc801147/attachment.htm>


More information about the notifications mailing list