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

Minor fixed to documents and C comments.

Browse Source
This commit is contained in:
Gregory Nutt 2019-02-23 17:44:34 -06:00
parent 8de101ca18
commit 11eb7ef4f8
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/NuttX.html
View File

@ -1757,10 +1757,10 @@
<li>STMicroelectronics
<ul>
<li><a href="#str71x">STMicro STR71x</a> <small>(ARM7TDMI)</small></li>
<li><a href="#stm32f0xx">STMicro STM32F0xx</a> <small>(STM32 F0, ARM Cortex-M0)</small></li>
<li><a href="#stm32L0xx">STMicro STM32L0xx</a> <small>(STM32 L0, ARM Cortex-M0)</small></li>
<li><a href="#stm32l152">STMicro STM32L152</a> <small>(STM32 L1 &quot;EnergyLite&quot; Line, ARM Cortex-M3)</small></li>
<li><a href="#stm32l162">STMicro STM32L162</a> <small>(STM32 L1 &quot;EnergyLite&quot; Medium+ Density, ARM Cortex-M3)</small></li>
<li><a href="#stm32f0xx">STMicro STM32F0xx</a> <small>(STM32 F0, ARM Cortex-M0)</small></li>
<li><a href="#stm32L0xx">STMicro STM32L0xx</a> <small>(STM32 F0, ARM Cortex-M0)</small></li>
<li><a href="#stm32f100x">STMicro STM32F100x</a> <small>(STM32 F1 &quot;Value Line&quot;Family, ARM Cortex-M3)</small></li>
<li><a href="#stm32f102x">STMicro STM32F102x</a> <small>(STM32 F1 Family, ARM Cortex-M3)</small></li>
<li><a href="#stm32f103cx">STMicro STM32F103C4/C8</a> <small>(STM32 F1 &quot;Low- and Medium-Density Line&quot; Family, ARM Cortex-M3)</small></li>
@ -3223,7 +3223,7 @@ nsh>
<td><br></td>
<td>
<p>
<a name="stm32L0xx"><b>STMicro STM32L0xx (STM32 F0, ARM Cortex-M0)</b>.</a>
<a name="stm32L0xx"><b>STMicro STM32L0xx (STM32 L0, ARM Cortex-M0)</b>.</a>
Support for the STM32 FL family was contributed by Mateusz Sfafoni in NuttX-7.28.
There are ports to two different STM32 L0 boards in the repository:
</p>

2
sched/sched/sched_waitpid.c
View File

@ -507,7 +507,7 @@ pid_t waitpid(pid_t pid, int *stat_loc, int options)
if (rtcb->group->tg_nchildren == 0 ||
(pid != (pid_t)-1 && (ret = nxsig_kill(pid, 0)) < 0))
{
/* We know that the child task was running okay we started,
/* We know that the child task was running okay when we started,
* so we must have lost the signal. What can we do?
* Let's return ECHILD.. that is at least informative.
*/