len0rd/FreeRTOS-Kernel
1
0
Fork 0
mirror of https://github.com/FreeRTOS/FreeRTOS-Kernel.git synced 2025-05-21 04:29:04 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fix spelling issues.

Browse source
This commit is contained in:
Yuhui.Zheng 2020-02-07 19:19:47 +00:00
parent 28efb5449c
commit f988394e0d
3 changed files with 9 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
FreeRTOS/Source/include/FreeRTOS.h
View file

@ -241,7 +241,7 @@ extern "C" {
#define configASSERT_DEFINED 1 #define configASSERT_DEFINED 1
#endif #endif
/* configPRECONDITION should be resolve to configASSERT. /* configPRECONDITION should be defined as configASSERT.
The CBMC proofs need a way to track assumptions and assertions. The CBMC proofs need a way to track assumptions and assertions.
A configPRECONDITION statement should express an implicit invariant or A configPRECONDITION statement should express an implicit invariant or
assumption made. A configASSERT statement should express an invariant that must assumption made. A configASSERT statement should express an invariant that must

2
FreeRTOS/Source/include/task.h
View file

@ -2213,7 +2213,7 @@ BaseType_t xTaskNotifyStateClear( TaskHandle_t xTask );
* Clears the bits specified by the ulBitsToClear bit mask in the notification * Clears the bits specified by the ulBitsToClear bit mask in the notification
* value of the task referenced by xTask. * value of the task referenced by xTask.
* *
* Set ulBitsToClear to to 0xffffffff (UINT_MAX on 32-bit architectures) to clear * Set ulBitsToClear to 0xffffffff (UINT_MAX on 32-bit architectures) to clear
* the notification value to 0. Set ulBitsToClear to 0 to query the task's * the notification value to 0. Set ulBitsToClear to 0 to query the task's
* notification value without clearing any bits. * notification value without clearing any bits.
* *

15
FreeRTOS/Source/portable/MSVC-MingW/port.c
View file

@ -95,7 +95,7 @@ typedef struct
/* Handle of the thread that executes the task. */ /* Handle of the thread that executes the task. */
void *pvThread; void *pvThread;
/* Event used to makes sure the thread does not execute past a yield point /* Event used to make sure the thread does not execute past a yield point
between the call to SuspendThread() to suspend the thread and the between the call to SuspendThread() to suspend the thread and the
asynchronous SuspendThread() operation actually being performed. */ asynchronous SuspendThread() operation actually being performed. */
void *pvYieldEvent; void *pvYieldEvent;
@ -394,7 +394,7 @@ CONTEXT xContext;
xInsideInterrupt = pdFALSE; xInsideInterrupt = pdFALSE;
WaitForMultipleObjects( sizeof( pvObjectList ) / sizeof( void * ), pvObjectList, TRUE, INFINITE ); WaitForMultipleObjects( sizeof( pvObjectList ) / sizeof( void * ), pvObjectList, TRUE, INFINITE );
/* Cannot be in a critical section to get here. Tasks that exist a /* Cannot be in a critical section to get here. Tasks that exit a
critical section will block on a yield mutex to wait for an interrupt to critical section will block on a yield mutex to wait for an interrupt to
process if an interrupt was set pending while the task was inside the process if an interrupt was set pending while the task was inside the
critical section. xInsideInterrupt prevents interrupts that contain critical section. xInsideInterrupt prevents interrupts that contain
@ -456,12 +456,11 @@ CONTEXT xContext;
/* Ensure the thread is actually suspended by performing a /* Ensure the thread is actually suspended by performing a
synchronous operation that can only complete when the thread is synchronous operation that can only complete when the thread is
actually suspended. The below code asks for dummy register actually suspended. The code below asks for dummy register
data. Experimentation shows that these two lines don't appear data. Experimentation shows that these two lines don't appear
to do anything now, but according to to do anything now, but according to
https://devblogs.microsoft.com/oldnewthing/20150205-00/?p=44743 https://devblogs.microsoft.com/oldnewthing/20150205-00/?p=44743
they do - so as they do not harm (slight run-time hit) they have they do - so as they do not harm (slight run-time hit). */
been left it. */
xContext.ContextFlags = CONTEXT_INTEGER; xContext.ContextFlags = CONTEXT_INTEGER;
( void ) GetThreadContext( pxThreadState->pvThread, &xContext ); ( void ) GetThreadContext( pxThreadState->pvThread, &xContext );
@ -599,7 +598,7 @@ ThreadState_t *pxThreadState = ( ThreadState_t *) *( ( size_t * ) pxCurrentTCB )
ReleaseMutex( pvInterruptEventMutex ); ReleaseMutex( pvInterruptEventMutex );
if( ulCriticalNesting == portNO_CRITICAL_NESTING ) if( ulCriticalNesting == portNO_CRITICAL_NESTING )
{ {
/* An interrupt was pended so ensure to block to alow it to /* An interrupt was pended so ensure to block to allow it to
execute. In most cases the (simulated) interrupt will have execute. In most cases the (simulated) interrupt will have
executed before the next line is reached - so this is just to make executed before the next line is reached - so this is just to make
sure. */ sure. */
@ -669,7 +668,7 @@ int32_t lMutexNeedsReleasing, lWaitForYield = pdFALSE;
pvInterruptEventMutex is released as it waits on both pvInterruptEventMutex is released as it waits on both
pvInterruptEventMutex and pvInterruptEvent. pvInterruptEventMutex and pvInterruptEvent.
pvInterruptEvent is only set when the simulated pvInterruptEvent is only set when the simulated
interrupt is pendeded if the interrupt is pended interrupt is pended if the interrupt is pended
from outside a critical section - hence it is set from outside a critical section - hence it is set
here. */ here. */
SetEvent( pvInterruptEvent ); SetEvent( pvInterruptEvent );