From c1839a07aad2a73665c90ada40e4f9dc80fc0a08 Mon Sep 17 00:00:00 2001 From: David Sidrane Date: Sun, 8 Mar 2020 05:51:34 -0700 Subject: [PATCH] task_exit.c:Fix style errors. --- sched/task/task_exit.c | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/sched/task/task_exit.c b/sched/task/task_exit.c index 4ac4d54cd9..78af294f5a 100644 --- a/sched/task/task_exit.c +++ b/sched/task/task_exit.c @@ -64,9 +64,9 @@ * never be called from normal user code, but only from the architecture- * specific implementation of exit. * - * Threads/tasks could also be terminated via pthread_cancel, task_delete(), - * and task_restart(). In the last two cases, the task will be terminated - * as though exit() were called. + * Threads/tasks could also be terminated via pthread_cancel, + * task_delete(), and task_restart(). In the last two cases, the + * task will be terminated as though exit() were called. * * Input Parameters: * None @@ -100,12 +100,12 @@ int nxtask_exit(void) dtcb = this_task(); #endif - /* Remove the TCB of the current task from the ready-to-run list. A context - * switch will definitely be necessary -- that must be done by the - * architecture-specific logic. + /* Remove the TCB of the current task from the ready-to-run list. A + * context switch will definitely be necessary -- that must be done + * by the architecture-specific logic. * - * sched_removereadytorun will mark the task at the head of the ready-to-run - * with state == TSTATE_TASK_RUNNING + * sched_removereadytorun will mark the task at the head of the + * ready-to-run with state == TSTATE_TASK_RUNNING */ sched_removereadytorun(dtcb); @@ -147,9 +147,10 @@ int nxtask_exit(void) rtcb->task_state = TSTATE_TASK_READYTORUN; /* Move the TCB to the specified blocked task list and delete it. Calling - * nxtask_terminate with non-blocking true will suppress atexit() and on-exit() - * calls and will cause buffered I/O to fail to be flushed. The former - * is required _exit() behavior; the latter is optional _exit() behavior. + * nxtask_terminate with non-blocking true will suppress atexit() and + * on-exit() calls and will cause buffered I/O to fail to be flushed. The + * former is required _exit() behavior; the latter is optional _exit() + * behavior. */ sched_addblocked(dtcb, TSTATE_TASK_INACTIVE);