tree 9671528fb73ea6cd6c79b091665625be528fe9ef
parent c6636f465f2bc70a31963356e549ebf514f892c3
author Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com> 1603411775 -0700
committer GitHub <noreply@github.com> 1603411775 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfkh8/CRBK7hj4Ov3rIwAAdHIIAI6RlZb+BwWMLKBLn+oZi+j2
 npWx/mF92blc044O6NSU917WKLglQp1EyfHGLrU1raotEiBZxu/2IGNW4DpfMQEt
 DwMieGdaPJzRTE2Z/0shzi9RBxD3zh4egQDNl/qoUqavEMjlFzITycFkyyIi6hS+
 pWj3YPWv17V7nPXdXc57q9NVVxADrbkEfl6tEkDGvpr9sCLLQIzlUQ6A2g7MnjW7
 ilqjefApROiR9ZLjchQNkj+v3ywNzOecOVZEBSR3SMtDqQclt1HfwbNTlPSGYi5X
 GWX5shasH+/DsH8wN9JtKAD2LO8vGC9oVzw42hADrwZRECD05dOXUHrMkR0iP6M=
 =KxAH
 -----END PGP SIGNATURE-----
 

Fix missed yield in xTaskResumeFromISR (#207)

If a higher priority task than the currently running task was resumed
using xTaskResumeFromISR and the user chose to ignore the return value
of xTaskResumeFromISR to initiate a context switch using
portYIELD_FROM_ISR, we were not doing the context switch on the next run
of the scheduler. This change fixes this by marking a yield as pending
to ensure that the context switch is performed on the next run of the
scheduler.

Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com>