doc: fix some typos
PATCH 1/1 doc: fix some typos
Fix some typos in documentation.
Signed-off-by Xishi Qiu <[email protected]>
--- Documentation/IRQ-domain.txt | 2 +- Documentation/email-clients.txt | 2 +- Documentation/io-mapping.txt | 2 +- Documentation/kprobes.txt | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)
Documentation/IRQ-domain.txt +1 -1
@@ -141,7 +141,7 @@ will use a legacy domain only if an IRQ range is supplied by the system and will otherwise use a linear domain mapping. The semantics of this call are such that if an IRQ range is specified then descriptors will be allocated on-the-fly for it, and if no range is -specified it will fall through to irq_domain_add_linear() which meand +specified it will fall through to irq_domain_add_linear() which means *no* irq descriptors will be allocated. A typical use case for simple domains is where an irqchip provider
Documentation/email-clients.txt +1 -1
@@ -104,7 +104,7 @@ Then from the "Message" menu item, select insert file and choose your patch. As an added bonus you can customise the message creation toolbar menu and put the "insert file" icon there. -Make the the composer window wide enough so that no lines wrap. As of +Make the composer window wide enough so that no lines wrap. As of KMail 1.13.5 (KDE 4.5.4), KMail will apply word wrapping when sending the email if the lines wrap in the composer window. Having word wrapping disabled in the Options menu isn't enough. Thus, if your patch has very
Documentation/io-mapping.txt +1 -1
@@ -38,7 +38,7 @@ maps are more efficient: void io_mapping_unmap_atomic(void *vaddr) - 'vaddr' must be the the value returned by the last + 'vaddr' must be the value returned by the last io_mapping_map_atomic_wc call. This unmaps the specified page and allows the task to sleep once again.
Documentation/kprobes.txt +1 -1
@@ -92,7 +92,7 @@ stack contents as the probed function. When it is done, the handler calls jprobe_return(), which traps again to restore the original stack contents and processor state and switch to the probed function. -By convention, the callee owns its arguments, so gcc may produce code +By convention, the caller owns its arguments, so gcc may produce code that unexpectedly modifies that portion of the stack. This is why Kprobes saves a copy of the stack and restores it after the jprobe handler has run. Up to MAX_STACK_SIZE bytes are copied -- e.g.,
Signature · 1 line
1.7.1
Randy Dunlap
reviewerDocumentation/kprobes.txt stack contents as the probed function. When it is done, the handler · line 95
Quoted 9 lines · Xishi Qiu
Documentation/kprobes.txt +0
-1@@ -92,7 +92,7 @@ stack contents as the probed function. When it is done, the handler calls jprobe_return(), which traps again to restore the original stack contents and processor state and switch to the probed function. -By convention, the callee owns its arguments, so gcc may produce code
Are you sure about that?
It looks correct to me (before the patch).
Quoted 5 lines
Documentation/kprobes.txt +1
-0+By convention, the caller owns its arguments, so gcc may produce code that unexpectedly modifies that portion of the stack. This is why Kprobes saves a copy of the stack and restores it after the jprobe handler has run. Up to MAX_STACK_SIZE bytes are copied -- e.g.,
Signature · 1 line
~Randy
Quoted 10 lines · Randy Dunlap
Quoted 8 lines · Xishi Qiu
Documentation/kprobes.txt +0
-0@@ -92,7 +92,7 @@ stack contents as the probed function. When it is done, the handler calls jprobe_return(), which traps again to restore the original stack contents and processor state and switch to the probed function.
Quoted 5 lines
Documentation/kprobes.txt stack contents as the probed function. When it is done, the handler · line 95
Quoted 1 line
Documentation/kprobes.txt +0
-1-By convention, the callee owns its arguments, so gcc may produce codeAre you sure about that?
It looks correct to me (before the patch).
Hi Randy, you are right, I confused caller and callee.
Thanks,
Xishi Qiu
Quoted 7 lines
Quoted 5 lines
Documentation/kprobes.txt +1
-0+By convention, the caller owns its arguments, so gcc may produce code that unexpectedly modifies that portion of the stack. This is why Kprobes saves a copy of the stack and restores it after the jprobe handler has run. Up to MAX_STACK_SIZE bytes are copied -- e.g.,