Be sure to register a new mutex owner _before_ waking it. Won't be an issue now but...
commitceabd029bfee447f90e02d3deb5acbc0401dd115
authorjethead71 <jethead71@a1c6a512-1295-4272-9138-f99709370657>
Sun, 21 Oct 2007 19:10:03 +0000 (21 19:10 +0000)
committerjethead71 <jethead71@a1c6a512-1295-4272-9138-f99709370657>
Sun, 21 Oct 2007 19:10:03 +0000 (21 19:10 +0000)
tree2644e1ca78bec0c345d790d23c1c93ebcd709558
parent030ca2d0a594d0b5c5b541328591b884ac341368
Be sure to register a new mutex owner _before_ waking it. Won't be an issue now but would be with mutex recursion on one used for > 1 core where ownership transfer and cs entry/recursion are allowed to run in parallel (by design). TODO: Add true exchange to wakeup_thread but that's not really important for the time being.

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@15251 a1c6a512-1295-4272-9138-f99709370657
firmware/kernel.c