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

Fix "with with" typos

Browse Source 
In many cases, remove one of them.
In a few places, it looks like a typo of "width" actually.
This commit is contained in:
YAMAMOTO Takashi 2020-01-27 13:55:23 +09:00 committed by Alin Jerpelea
parent e02c14a926
commit 83354983c3
12 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/NXGraphicsSubsystem.html
View File

@ -3852,7 +3852,7 @@ int nxcursor_setposition(NXHANDLE hnd, FAR const struct nxgl_point_s *pos);
<ul>
<dl>
<dt><code>CONFIG_NXTK_BORDERWIDTH</code>:
<dd>Specifies with with of the border (in pixels) used with
<dd>Specifies the width of the border (in pixels) used with
framed windows. The default is 4.
<dt><code>CONFIG_NXTK_BORDERCOLOR1</code>, <code>CONFIG_NXTK_BORDERCOLOR2</code>, and <code>CONFIG_NXTK_BORDERCOLOR3</code>:
<dd>Specify the colors of the border used with framed windows.

2
boards/arm/stm32/stm32f103-minimum/src/stm32_lcd_backpack.c
View File

@ -85,7 +85,7 @@ int stm32_lcd_backpack_init(FAR const char *devpath)
* Note: We are using the LCD_I2C_BACKPACK_CFG_SAINSMART config that
* defined the I2C Address to 0x27 to PCF8574. Double check if all
* the bits (pins) from PCF8574 connected to the LCD controller
* are correct with with this LCD CFG definition.
* are correct with this LCD CFG definition.
*/
cfg.rows = 2;

2
boards/arm/stm32/stm32f4discovery/README.txt
View File

@ -2147,7 +2147,7 @@ Configuration Sub-directories
+CONFIG_EXAMPLES_NXLINES_BPP=1
+CONFIG_EXAMPLES_NXLINES_EXTERNINIT=y
There are some issues with with the presentation... some tuning of the
There are some issues with the presentation... some tuning of the
configuration could fix that. Lower resolution displays are also more
subject to the "fat, flat line bug" that I need to fix someday. See
http://www.nuttx.org/doku.php?id=wiki:graphics:nxgraphics for a description

2
boards/avr/at90usb/micropendous3/README.txt
View File

@ -161,7 +161,7 @@ DFU Bootloader
^^^^^^^^^^^^^^
There is also an DFU bootloader that resides in the upper 8Kb of FLASH
(unless you ERASE the flash with with ICE). You can enter this bootloader
(unless you ERASE the flash with ICE). You can enter this bootloader
(if it is in FLASH) by:
Holding both the SW1 (RESET) and SW2, then releasing SW1 while continuing

2
drivers/rwbuffer.c
View File

@ -177,7 +177,7 @@ static void rwb_wrtimeout(FAR void *arg)
finfo("Timeout!\n");
/* If a timeout elapses with with write buffer activity, this watchdog
/* If a timeout elapses with write buffer activity, this watchdog
* handler function will be evoked on the thread of execution of the
* worker thread.
*/

2
fs/unionfs/fs_unionfs.c
View File

@ -2278,7 +2278,7 @@ static int unionfs_unlink(FAR struct inode *mountpt,
else
{
/* Check if the file exists with with name on file system 2. The only
/* Check if the file exists with name on file system 2. The only
* reason that we check here is so that we can return the more
* meaningful -ENOSYS if file system 2 is a read-only file system.
*/

2
graphics/Kconfig
View File

@ -299,7 +299,7 @@ config NXTK_BORDERWIDTH
int "Border Width"
default 4
---help---
Specifies with with of the border (in pixels) used with framed windows.
Specifies the width of the border (in pixels) used with framed windows.
The default is 4.
config NXTK_DEFAULT_BORDERCOLORS

2
graphics/README.txt
View File

@ -138,7 +138,7 @@ CONFIG_NX_XYINPUT
CONFIG_NX_KBD
Build in support of keypad/keyboard input.
CONFIG_NXTK_BORDERWIDTH
Specifies with with of the border (in pixels) used with framed windows.
Specifies the width of the border (in pixels) used with framed windows.
The default is 4.
CONFIG_NXTK_BORDERCOLOR1, CONFIG_NXTK_BORDERCOLOR2, CONFIG_NXTK_BORDERCOLOR3
Specify the colors of the border used with framed windows.

2
graphics/vnc/server/vnc_color.c
View File

@ -375,7 +375,7 @@ int vnc_colors(FAR struct vnc_session_s *session, FAR struct nxgl_rect_s *rect,
for (pixndx = 0; pixndx < ncolors - 1; pixndx++)
{
/* Compare color N with with colors M={(N_1)..ncolors} */
/* Compare color N with colors M={(N_1)..ncolors} */
maxndx = pixndx;
for (cmpndx = maxndx + 1; cmpndx < ncolors; cmpndx++)

2
include/nuttx/net/ethernet.h
View File

@ -67,7 +67,7 @@
#define TPID_8021QVLAN 0x8100
/* These are some of the types then associated with withe QVLAN tagged
/* These are some of the types associated with QVLAN tagged
* Ethernet packets.
*/

2
libs/libc/README.txt
View File

@ -13,7 +13,7 @@ more like on multi-threaded program that all runs in kernel-mode.
But if the CONFIG_BUILD_PROTECTED option is selected, NuttX will be built
into distinct user-mode and kernel-mode sections. In that case, most of the
code in the nuttx/ directory will run in kernel-mode with with exceptions
code in the nuttx/ directory will run in kernel-mode with exceptions
of (1) the user-mode "proxies" found in syscall/proxies, and (2) the
standard C library functions found in this directory. In this build model,
it is critical to separate the user-mode OS interfaces in this way.

4
sched/task/task_exithook.c
View File

@ -647,7 +647,7 @@ void nxtask_exithook(FAR struct tcb_s *tcb, int status, bool nonblocking)
* a bug.
* 2. We cannot call the exit functions if nonblocking is requested: These
* functions might block.
* 3. This function will only be called with with non-blocking == true
* 3. This function will only be called with non-blocking == true
* only when called through _exit(). _exit() behaviors requires that
* the exit functions *not* be called.
*/
@ -682,7 +682,7 @@ void nxtask_exithook(FAR struct tcb_s *tcb, int status, bool nonblocking)
* NOTES:
* 1. We cannot flush the buffered I/O if nonblocking is requested.
* that might cause this logic to block.
* 2. This function will only be called with with non-blocking == true
* 2. This function will only be called with non-blocking == true
* only when called through _exit(). _exit() behavior does not
* require that the streams be flushed
*/