tree 45f44b8210a10d5efd28f0c0f2437097a217c34a
parent 287361091bee44770704ffa2b4ce2b7580ad716b
author RichardBarry <3073890+RichardBarry@users.noreply.github.com> 1597015137 -0700
committer GitHub <noreply@github.com> 1597015137 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfMIRhCRBK7hj4Ov3rIwAAdHIIAHVX9g2uaf8neNs2sxSMTJGp
 sv6iVJazIz+DvhatzhrmyBCCKAAHaX8vbKVl1X5UY1XpHn2cgEL4UmhQNKLT3frl
 MoZUUhzubktb8oweKh2KK0ru+IuqrvKMsnWAyv+1U2GALzbu0IgME+Li8c6g9J84
 cZTc/AwdEwrf0uhtiXVYPW8iqv++AlxZeNW/btDSbcsQNq/ZckjpIMqo43t8C4AZ
 aWEyh2/GyMuY7E207x4KZfw4xMHMQZlvQ1JsPVlst4/EdEdWZUDcQuLibq6ijYbT
 hkJeO/RMkf7MQLLZTXoN4BEQ+y6zeBfYqWKRMFP9xyz5gFPPidfLOtBIPd+Svjk=
 =01kG
 -----END PGP SIGNATURE-----
 

Fix: Two one line fixes, xTaskCheckForTimeOut() and ulTaskGenericNotifyValueClear(). (#82)

ulTaskGenericNotifyValueClear() returned the notification value of the
currently running task, not the target task.  Now it returns the
notification value of the target task.

Some users expected xTaskCheckForTimeOut() to clear the 'last wake time'
value each time a timeout occurred, whereas it only did that in one path.
It now clears the last wake time in all paths that return that a timeout
occurred.