sergiotarxz/nuttx
sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Some cosmetic updates, mostly to spacing and comments.

Browse Source
This commit is contained in:
Gregory Nutt 2018-12-30 11:58:19 -06:00
parent 1325c98f97
commit bdd02a6aed
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
include/nuttx/mm/mm.h
View File

@ -241,11 +241,11 @@ struct mm_heap_s
sem_t mm_semaphore; sem_t mm_semaphore;
pid_t mm_holder; pid_t mm_holder;
int mm_counts_held; int mm_counts_held;
/* This is the size of the heap provided to mm */ /* This is the size of the heap provided to mm */
size_t mm_heapsize; size_t mm_heapsize;
/* This is the first and last nodes of the heap */ /* This is the first and last nodes of the heap */

5
sched/task/task_getpid.c
View File

@ -40,6 +40,7 @@
#include <sys/types.h> #include <sys/types.h>
#include <unistd.h> #include <unistd.h>
#include <sched.h> #include <sched.h>
#include <errno.h>
#include "sched/sched.h" #include "sched/sched.h"
#include "task/task.h" #include "task/task.h"
@ -66,7 +67,7 @@
* getpid(), however, may be called from within the OS in some cases. * getpid(), however, may be called from within the OS in some cases.
* There are certain situations during context switching when the OS data * There are certain situations during context switching when the OS data
* structures are in flux and where the current task at the head of the * structures are in flux and where the current task at the head of the
* ready-to-run task list) is not actually running. In that case, * ready-to-run task list is not actually running. In that case,
* getpid() will return the error: -ESRCH * getpid() will return the error: -ESRCH
* *
****************************************************************************/ ****************************************************************************/
@ -80,7 +81,7 @@ pid_t getpid(void)
* exceptions to this: * exceptions to this:
* *
* 1. Early in the start-up sequence, the ready-to-run list may be * 1. Early in the start-up sequence, the ready-to-run list may be
* empty! This case, of course, the CPU0 start-up/IDLE thread with * empty! In this case, of course, the CPU0 start-up/IDLE thread with
* pid == 0 must be running, and * pid == 0 must be running, and
* 2. As described above, during certain context-switching conditions the * 2. As described above, during certain context-switching conditions the
* task at the head of the ready-to-run list may not actually be * task at the head of the ready-to-run list may not actually be