xTaskGenericNotify() now sets xYieldPending to pdTRUE even when the 'higher priority...

[freertos] / FreeRTOS / Demo / WIN32-MSVC / main_blinky.c

diff --git a/FreeRTOS/Demo/WIN32-MSVC/main_blinky.c b/FreeRTOS/Demo/WIN32-MSVC/main_blinky.c
index a90731f0e9ecde2bb1fa1ec3be7e45b3c6e6fa0b..cdfdbed3ff900be967b47ed4e922941465195df6 100644 (file)
--- a/FreeRTOS/Demo/WIN32-MSVC/main_blinky.c
+++ b/FreeRTOS/Demo/WIN32-MSVC/main_blinky.c
@@ -240,7 +240,7 @@ uint32_t ulReceivedValue;
                is it an expected value?  Normally calling printf() from a task is not\r
                a good idea.  Here there is lots of stack space and only one task is\r
                using console IO so it is ok.  However, note the comments at the top of\r
-               this file about the risks of making Windows system calls (such as \r
+               this file about the risks of making Windows system calls (such as\r
                console output) from a FreeRTOS task. */\r
                if( ulReceivedValue == mainVALUE_SENT_FROM_TASK )\r
                {\r