Commit df5cbb27836ff6a6c807f9030ca536403fc674d2
Committed by
Jiri Kosina
1 parent
2509671dcf
Exists in
master
and in
13 other branches
doc: fix double words
Fix double words "the the" in various files within Documentations. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Showing 12 changed files with 12 additions and 12 deletions Side-by-side Diff
- Documentation/filesystems/autofs4-mount-control.txt
- Documentation/futex-requeue-pi.txt
- Documentation/input/multi-touch-protocol.txt
- Documentation/kmemcheck.txt
- Documentation/memory-barriers.txt
- Documentation/networking/spider_net.txt
- Documentation/power/devices.txt
- Documentation/security/Smack.txt
- Documentation/trace/ring-buffer-design.txt
- Documentation/usb/WUSB-Design-overview.txt
- Documentation/virtual/kvm/api.txt
- Documentation/vm/unevictable-lru.txt
Documentation/filesystems/autofs4-mount-control.txt
... | ... | @@ -255,7 +255,7 @@ |
255 | 255 | |
256 | 256 | Obtain and release a file descriptor for an autofs managed mount point |
257 | 257 | path. The open call requires an initialized struct autofs_dev_ioctl with |
258 | -the the path field set and the size field adjusted appropriately as well | |
258 | +the path field set and the size field adjusted appropriately as well | |
259 | 259 | as the arg1 field set to the device number of the autofs mount. The |
260 | 260 | device number can be obtained from the mount options shown in |
261 | 261 | /proc/mounts. The close call requires an initialized struct |
Documentation/futex-requeue-pi.txt
Documentation/input/multi-touch-protocol.txt
... | ... | @@ -372,7 +372,7 @@ |
372 | 372 | |
373 | 373 | Rationale: We have no information about the orientation of the touching |
374 | 374 | ellipse, so approximate it with an inscribed circle instead. The tool |
375 | -ellipse should align with the the vector (T - C), so the diameter must | |
375 | +ellipse should align with the vector (T - C), so the diameter must | |
376 | 376 | increase with distance(T, C). Finally, assume that the touch diameter is |
377 | 377 | equal to the tool thickness, and we arrive at the formulas above. |
378 | 378 |
Documentation/kmemcheck.txt
... | ... | @@ -541,7 +541,7 @@ |
541 | 541 | 92 } _sifields; |
542 | 542 | 93 } siginfo_t; |
543 | 543 | |
544 | -On 64-bit, the int is 4 bytes long, so it must the the union member that has | |
544 | +On 64-bit, the int is 4 bytes long, so it must the union member that has | |
545 | 545 | not been initialized. We can verify this using gdb: |
546 | 546 | |
547 | 547 | $ gdb vmlinux |
Documentation/memory-barriers.txt
... | ... | @@ -1371,7 +1371,7 @@ |
1371 | 1371 | process_message(msg); |
1372 | 1372 | } |
1373 | 1373 | |
1374 | - There is nothing to prevent the the compiler from transforming | |
1374 | + There is nothing to prevent the compiler from transforming | |
1375 | 1375 | process_level() to the following, in fact, this might well be a |
1376 | 1376 | win for single-threaded code: |
1377 | 1377 |
Documentation/networking/spider_net.txt
... | ... | @@ -73,7 +73,7 @@ |
73 | 73 | all be pointing at the same descr, which should be "empty". All of the |
74 | 74 | other descrs in the ring should be "empty" as well. |
75 | 75 | |
76 | -The show_rx_chain() routine will print out the the locations of the | |
76 | +The show_rx_chain() routine will print out the locations of the | |
77 | 77 | GDACTDPA, tail and head pointers. It will also summarize the contents |
78 | 78 | of the ring, starting at the tail pointer, and listing the status |
79 | 79 | of the descrs that follow. |
Documentation/power/devices.txt
... | ... | @@ -391,7 +391,7 @@ |
391 | 391 | the resume methods. This generally involves undoing the actions of the |
392 | 392 | preceding suspend_late phase. |
393 | 393 | |
394 | - 3 The resume methods should bring the the device back to its operating | |
394 | + 3 The resume methods should bring the device back to its operating | |
395 | 395 | state, so that it can perform normal I/O. This generally involves |
396 | 396 | undoing the actions of the suspend phase. |
397 | 397 |
Documentation/security/Smack.txt
... | ... | @@ -3,7 +3,7 @@ |
3 | 3 | "Good for you, you've decided to clean the elevator!" |
4 | 4 | - The Elevator, from Dark Star |
5 | 5 | |
6 | -Smack is the the Simplified Mandatory Access Control Kernel. | |
6 | +Smack is the Simplified Mandatory Access Control Kernel. | |
7 | 7 | Smack is a kernel based implementation of mandatory access |
8 | 8 | control that includes simplicity in its primary design goals. |
9 | 9 |
Documentation/trace/ring-buffer-design.txt
... | ... | @@ -683,7 +683,7 @@ |
683 | 683 | cmpxchg(tail_page, temp_page, next_page) |
684 | 684 | |
685 | 685 | The above will update the tail page if it is still pointing to the expected |
686 | -page. If this fails, a nested write pushed it forward, the the current write | |
686 | +page. If this fails, a nested write pushed it forward, the current write | |
687 | 687 | does not need to push it. |
688 | 688 | |
689 | 689 |
Documentation/usb/WUSB-Design-overview.txt
... | ... | @@ -25,7 +25,7 @@ |
25 | 25 | * Design-overview.txt-1.8 |
26 | 26 | |
27 | 27 | This code implements a Ultra Wide Band stack for Linux, as well as |
28 | -drivers for the the USB based UWB radio controllers defined in the | |
28 | +drivers for the USB based UWB radio controllers defined in the | |
29 | 29 | Wireless USB 1.0 specification (including Wireless USB host controller |
30 | 30 | and an Intel WiNET controller). |
31 | 31 |
Documentation/virtual/kvm/api.txt
... | ... | @@ -1462,7 +1462,7 @@ |
1462 | 1462 | char regs[KVM_APIC_REG_SIZE]; |
1463 | 1463 | }; |
1464 | 1464 | |
1465 | -Copies the input argument into the the Local APIC registers. The data format | |
1465 | +Copies the input argument into the Local APIC registers. The data format | |
1466 | 1466 | and layout are the same as documented in the architecture manual. |
1467 | 1467 | |
1468 | 1468 |
Documentation/vm/unevictable-lru.txt
... | ... | @@ -453,7 +453,7 @@ |
453 | 453 | mmap(MAP_LOCKED) SYSTEM CALL HANDLING |
454 | 454 | ------------------------------------- |
455 | 455 | |
456 | -In addition the the mlock()/mlockall() system calls, an application can request | |
456 | +In addition the mlock()/mlockall() system calls, an application can request | |
457 | 457 | that a region of memory be mlocked supplying the MAP_LOCKED flag to the mmap() |
458 | 458 | call. Furthermore, any mmap() call or brk() call that expands the heap by a |
459 | 459 | task that has previously called mlockall() with the MCL_FUTURE flag will result |