diff options
author | Xishi Qiu <qiuxishi@huawei.com> | 2013-11-06 16:18:19 -0500 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2013-12-02 08:48:28 -0500 |
commit | d9a6ed1fa43859a5eb94725b6c9565f8cbd113ab (patch) | |
tree | 50b42f78569760cc2bb15cb96ba958adf7c524e5 | |
parent | ff18dd8f1c7579d8b013705877c9bf4260770822 (diff) |
doc: fix some typos
Fix some typos in three documentations.
Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
Acked-by: Rob Landley <rob@landley.net>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
-rw-r--r-- | Documentation/IRQ-domain.txt | 2 | ||||
-rw-r--r-- | Documentation/email-clients.txt | 2 | ||||
-rw-r--r-- | Documentation/io-mapping.txt | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/IRQ-domain.txt b/Documentation/IRQ-domain.txt index 9bc95942ec22..03df71aeb38c 100644 --- a/Documentation/IRQ-domain.txt +++ b/Documentation/IRQ-domain.txt | |||
@@ -141,7 +141,7 @@ will use a legacy domain only if an IRQ range is supplied by the | |||
141 | system and will otherwise use a linear domain mapping. The semantics | 141 | system and will otherwise use a linear domain mapping. The semantics |
142 | of this call are such that if an IRQ range is specified then | 142 | of this call are such that if an IRQ range is specified then |
143 | descriptors will be allocated on-the-fly for it, and if no range is | 143 | descriptors will be allocated on-the-fly for it, and if no range is |
144 | specified it will fall through to irq_domain_add_linear() which meand | 144 | specified it will fall through to irq_domain_add_linear() which means |
145 | *no* irq descriptors will be allocated. | 145 | *no* irq descriptors will be allocated. |
146 | 146 | ||
147 | A typical use case for simple domains is where an irqchip provider | 147 | A typical use case for simple domains is where an irqchip provider |
diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt index 860c29a472ad..e9f5daccbd02 100644 --- a/Documentation/email-clients.txt +++ b/Documentation/email-clients.txt | |||
@@ -104,7 +104,7 @@ Then from the "Message" menu item, select insert file and choose your patch. | |||
104 | As an added bonus you can customise the message creation toolbar menu | 104 | As an added bonus you can customise the message creation toolbar menu |
105 | and put the "insert file" icon there. | 105 | and put the "insert file" icon there. |
106 | 106 | ||
107 | Make the the composer window wide enough so that no lines wrap. As of | 107 | Make the composer window wide enough so that no lines wrap. As of |
108 | KMail 1.13.5 (KDE 4.5.4), KMail will apply word wrapping when sending | 108 | KMail 1.13.5 (KDE 4.5.4), KMail will apply word wrapping when sending |
109 | the email if the lines wrap in the composer window. Having word wrapping | 109 | the email if the lines wrap in the composer window. Having word wrapping |
110 | disabled in the Options menu isn't enough. Thus, if your patch has very | 110 | disabled in the Options menu isn't enough. Thus, if your patch has very |
diff --git a/Documentation/io-mapping.txt b/Documentation/io-mapping.txt index 473e43b2d588..5ca78426f54c 100644 --- a/Documentation/io-mapping.txt +++ b/Documentation/io-mapping.txt | |||
@@ -38,7 +38,7 @@ maps are more efficient: | |||
38 | 38 | ||
39 | void io_mapping_unmap_atomic(void *vaddr) | 39 | void io_mapping_unmap_atomic(void *vaddr) |
40 | 40 | ||
41 | 'vaddr' must be the the value returned by the last | 41 | 'vaddr' must be the value returned by the last |
42 | io_mapping_map_atomic_wc call. This unmaps the specified | 42 | io_mapping_map_atomic_wc call. This unmaps the specified |
43 | page and allows the task to sleep once again. | 43 | page and allows the task to sleep once again. |
44 | 44 | ||