yystopf
/
openharmony_kernel_liteos_m
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: fix typos 

Correct words function、procedure

close  https://gitee.com/openharmony/kernel_liteos_m/issues/I3RR6A
This commit is contained in:
rtos-lover 2021-05-19 14:49:13 +08:00
parent 930e92ebe2
commit 191644e441
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
kernel/src/los_mux.c
View File

@ -44,11 +44,11 @@ LITE_OS_SEC_BSS LosMuxCB* g_allMux = NULL;
LITE_OS_SEC_DATA_INIT LOS_DL_LIST g_unusedMuxList; LITE_OS_SEC_DATA_INIT LOS_DL_LIST g_unusedMuxList;
/***************************************************************************** /*****************************************************************************
Funtion : OsMuxInit Function : OsMuxInit
Description : Initializes the mutex Description : Initializes the mutex
Input : None Input : None
Output : None Output : None
Return : LOS_OK on success ,or error code on failure Return : LOS_OK on success, or error code on failure
*****************************************************************************/ *****************************************************************************/
LITE_OS_SEC_TEXT_INIT UINT32 OsMuxInit(VOID) LITE_OS_SEC_TEXT_INIT UINT32 OsMuxInit(VOID)
{ {
@ -80,7 +80,7 @@ LITE_OS_SEC_TEXT_INIT UINT32 OsMuxInit(VOID)
Description : Create a mutex Description : Create a mutex
Input : None Input : None
Output : muxHandle ------ Mutex operation handle Output : muxHandle ------ Mutex operation handle
Return : LOS_OK on success ,or error code on failure Return : LOS_OK on success, or error code on failure
*****************************************************************************/ *****************************************************************************/
LITE_OS_SEC_TEXT_INIT UINT32 LOS_MuxCreate(UINT32 *muxHandle) LITE_OS_SEC_TEXT_INIT UINT32 LOS_MuxCreate(UINT32 *muxHandle)
{ {
@ -121,7 +121,7 @@ ERR_HANDLER:
Description : Delete a mutex Description : Delete a mutex
Input : muxHandle ------Mutex operation handle Input : muxHandle ------Mutex operation handle
Output : None Output : None
Return : LOS_OK on success ,or error code on failure Return : LOS_OK on success, or error code on failure
*****************************************************************************/ *****************************************************************************/
LITE_OS_SEC_TEXT_INIT UINT32 LOS_MuxDelete(UINT32 muxHandle) LITE_OS_SEC_TEXT_INIT UINT32 LOS_MuxDelete(UINT32 muxHandle)
{ {
@ -181,7 +181,7 @@ STATIC_INLINE UINT32 OsMuxValidCheck(LosMuxCB *muxPended)
Input : muxHandle ------ Mutex operation handleone Input : muxHandle ------ Mutex operation handleone
: timeOut ------- waiting time : timeOut ------- waiting time
Output : None Output : None
Return : LOS_OK on success ,or error code on failure Return : LOS_OK on success, or error code on failure
*****************************************************************************/ *****************************************************************************/
LITE_OS_SEC_TEXT UINT32 LOS_MuxPend(UINT32 muxHandle, UINT32 timeout) LITE_OS_SEC_TEXT UINT32 LOS_MuxPend(UINT32 muxHandle, UINT32 timeout)
{ {
@ -257,7 +257,7 @@ ERROR_MUX_PEND:
Description : Specify the mutex V operation, Description : Specify the mutex V operation,
Input : muxHandle ------ Mutex operation handle Input : muxHandle ------ Mutex operation handle
Output : None Output : None
Return : LOS_OK on success ,or error code on failure Return : LOS_OK on success, or error code on failure
*****************************************************************************/ *****************************************************************************/
LITE_OS_SEC_TEXT UINT32 LOS_MuxPost(UINT32 muxHandle) LITE_OS_SEC_TEXT UINT32 LOS_MuxPost(UINT32 muxHandle)
{ {

2
kernel/src/los_sched.c
View File

@ -248,7 +248,7 @@ STATIC INLINE BOOL OsSchedScanTimerList(VOID)
* (per cpu) and ipc(mutex,sem and etc.)'s block at the same time, it can be waken * (per cpu) and ipc(mutex,sem and etc.)'s block at the same time, it can be waken
* up by either timeout or corresponding ipc it's waiting. * up by either timeout or corresponding ipc it's waiting.
* *
* Now synchronize sortlink preocedure is used, therefore the whole task scan needs * Now synchronize sortlink procedure is used, therefore the whole task scan needs
* to be protected, preventing another core from doing sortlink deletion at same time. * to be protected, preventing another core from doing sortlink deletion at same time.
*/ */