From: rtel Date: Thu, 17 May 2018 17:50:14 +0000 (+0000) Subject: Minor updates to comments only. X-Git-Tag: V10.1.0~24 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=f4c25685fef379d5c484c33797398900aeb1a7aa;p=freertos Minor updates to comments only. git-svn-id: https://svn.code.sf.net/p/freertos/code/trunk@2541 1d2547de-c912-0410-9cb9-b8ca96c0e9e2 --- diff --git a/FreeRTOS/Source/portable/GCC/IA32_flat/portmacro.h b/FreeRTOS/Source/portable/GCC/IA32_flat/portmacro.h index 230d94eb9..4f45a1151 100644 --- a/FreeRTOS/Source/portable/GCC/IA32_flat/portmacro.h +++ b/FreeRTOS/Source/portable/GCC/IA32_flat/portmacro.h @@ -244,19 +244,19 @@ BaseType_t xPortInstallInterruptHandler( ISR_Handler_t pxHandler, uint32_t ulVec This method can always be used. It is slightly more complex than method 1 but benefits from a faster interrupt entry time. */ - #warning config_USE_COMMON_INTERRUPT_ENTRY_POINT was not defined in FreeRTOSConfig.h and has been defaulted to 1. + #warning configUSE_COMMON_INTERRUPT_ENTRY_POINT was not defined in FreeRTOSConfig.h and has been defaulted to 1. #define configUSE_COMMON_INTERRUPT_ENTRY_POINT 1 #endif #ifndef configISR_STACK_SIZE - /* Interrupt entry code will switch the stack in use to a dedicated system + /* Interrupt entry code will switch the stack in use to a dedicated system stack. configISR_STACK_SIZE defines the number of 32-bit values that can be stored on the system stack, and must be large enough to hold a potentially nested interrupt stack frame. */ - #error configISE_STACK_SIZE was not defined in FreeRTOSConfig.h. + #error configISR_STACK_SIZE was not defined in FreeRTOSConfig.h. #endif #ifndef configMAX_API_CALL_INTERRUPT_PRIORITY diff --git a/FreeRTOS/Source/tasks.c b/FreeRTOS/Source/tasks.c index b6f4cccd6..41c47f8f2 100644 --- a/FreeRTOS/Source/tasks.c +++ b/FreeRTOS/Source/tasks.c @@ -1370,7 +1370,7 @@ static void prvAddNewTaskToReadyList( TCB_t *pxNewTCB ) { #if( configUSE_TASK_NOTIFICATIONS == 1 ) { - /* The task does not appear on the vent list item of + /* The task does not appear on the event list item of and of the RTOS objects, but could still be in the blocked state if it is waiting on its notification rather than waiting on an object. */