mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-12-29 09:16:33 +00:00
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>
This commit is contained in:
parent
2509671dcf
commit
df5cbb2783
@ -255,7 +255,7 @@ AUTOFS_DEV_IOCTL_OPENMOUNT and AUTOFS_DEV_IOCTL_CLOSEMOUNT
|
||||
|
||||
Obtain and release a file descriptor for an autofs managed mount point
|
||||
path. The open call requires an initialized struct autofs_dev_ioctl with
|
||||
the the path field set and the size field adjusted appropriately as well
|
||||
the path field set and the size field adjusted appropriately as well
|
||||
as the arg1 field set to the device number of the autofs mount. The
|
||||
device number can be obtained from the mount options shown in
|
||||
/proc/mounts. The close call requires an initialized struct
|
||||
|
@ -67,7 +67,7 @@ pthread_cond_wait_pi(cond, mutex)
|
||||
lock(cond->__data.__lock);
|
||||
} while(...)
|
||||
unlock(cond->__data.__lock);
|
||||
/* the kernel acquired the the mutex for us */
|
||||
/* the kernel acquired the mutex for us */
|
||||
}
|
||||
|
||||
pthread_cond_broadcast_pi(cond)
|
||||
|
@ -372,7 +372,7 @@ simple scheme, which is compatible with earlier usage, is:
|
||||
|
||||
Rationale: We have no information about the orientation of the touching
|
||||
ellipse, so approximate it with an inscribed circle instead. The tool
|
||||
ellipse should align with the the vector (T - C), so the diameter must
|
||||
ellipse should align with the vector (T - C), so the diameter must
|
||||
increase with distance(T, C). Finally, assume that the touch diameter is
|
||||
equal to the tool thickness, and we arrive at the formulas above.
|
||||
|
||||
|
@ -541,7 +541,7 @@ initialized. This is the beginning of the struct:
|
||||
92 } _sifields;
|
||||
93 } siginfo_t;
|
||||
|
||||
On 64-bit, the int is 4 bytes long, so it must the the union member that has
|
||||
On 64-bit, the int is 4 bytes long, so it must the union member that has
|
||||
not been initialized. We can verify this using gdb:
|
||||
|
||||
$ gdb vmlinux
|
||||
|
@ -1371,7 +1371,7 @@ code. Here are some examples of these sorts of optimizations:
|
||||
process_message(msg);
|
||||
}
|
||||
|
||||
There is nothing to prevent the the compiler from transforming
|
||||
There is nothing to prevent the compiler from transforming
|
||||
process_level() to the following, in fact, this might well be a
|
||||
win for single-threaded code:
|
||||
|
||||
|
@ -73,7 +73,7 @@ Thus, in an idle system, the GDACTDPA, tail and head pointers will
|
||||
all be pointing at the same descr, which should be "empty". All of the
|
||||
other descrs in the ring should be "empty" as well.
|
||||
|
||||
The show_rx_chain() routine will print out the the locations of the
|
||||
The show_rx_chain() routine will print out the locations of the
|
||||
GDACTDPA, tail and head pointers. It will also summarize the contents
|
||||
of the ring, starting at the tail pointer, and listing the status
|
||||
of the descrs that follow.
|
||||
|
@ -391,7 +391,7 @@ When resuming from freeze, standby or memory sleep, the phases are:
|
||||
the resume methods. This generally involves undoing the actions of the
|
||||
preceding suspend_late phase.
|
||||
|
||||
3 The resume methods should bring the the device back to its operating
|
||||
3 The resume methods should bring the device back to its operating
|
||||
state, so that it can perform normal I/O. This generally involves
|
||||
undoing the actions of the suspend phase.
|
||||
|
||||
|
@ -3,7 +3,7 @@
|
||||
"Good for you, you've decided to clean the elevator!"
|
||||
- The Elevator, from Dark Star
|
||||
|
||||
Smack is the the Simplified Mandatory Access Control Kernel.
|
||||
Smack is the Simplified Mandatory Access Control Kernel.
|
||||
Smack is a kernel based implementation of mandatory access
|
||||
control that includes simplicity in its primary design goals.
|
||||
|
||||
|
@ -683,7 +683,7 @@ against nested writers.
|
||||
cmpxchg(tail_page, temp_page, next_page)
|
||||
|
||||
The above will update the tail page if it is still pointing to the expected
|
||||
page. If this fails, a nested write pushed it forward, the the current write
|
||||
page. If this fails, a nested write pushed it forward, the current write
|
||||
does not need to push it.
|
||||
|
||||
|
||||
|
@ -25,7 +25,7 @@ updated content.
|
||||
* Design-overview.txt-1.8
|
||||
|
||||
This code implements a Ultra Wide Band stack for Linux, as well as
|
||||
drivers for the the USB based UWB radio controllers defined in the
|
||||
drivers for the USB based UWB radio controllers defined in the
|
||||
Wireless USB 1.0 specification (including Wireless USB host controller
|
||||
and an Intel WiNET controller).
|
||||
|
||||
|
@ -1462,7 +1462,7 @@ struct kvm_lapic_state {
|
||||
char regs[KVM_APIC_REG_SIZE];
|
||||
};
|
||||
|
||||
Copies the input argument into the the Local APIC registers. The data format
|
||||
Copies the input argument into the Local APIC registers. The data format
|
||||
and layout are the same as documented in the architecture manual.
|
||||
|
||||
|
||||
|
@ -453,7 +453,7 @@ putback_lru_page() function to add migrated pages back to the LRU.
|
||||
mmap(MAP_LOCKED) SYSTEM CALL HANDLING
|
||||
-------------------------------------
|
||||
|
||||
In addition the the mlock()/mlockall() system calls, an application can request
|
||||
In addition the mlock()/mlockall() system calls, an application can request
|
||||
that a region of memory be mlocked supplying the MAP_LOCKED flag to the mmap()
|
||||
call. Furthermore, any mmap() call or brk() call that expands the heap by a
|
||||
task that has previously called mlockall() with the MCL_FUTURE flag will result
|
||||
|
Loading…
Reference in New Issue
Block a user