aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems
diff options
context:
space:
mode:
authorDmitri Vorobiev <dmitri.vorobiev@gmail.com>2008-04-15 17:34:40 -0400
committerLinus Torvalds <torvalds@linux-foundation.org>2008-04-15 22:35:40 -0400
commitb82d4043b3550df00a036f6aa2c8ab9578a283ef (patch)
treea2d6686a074e14fee16da379e2b166c66da4cca3 /Documentation/filesystems
parent1f4deba80a0d9fa92832684e683335b742a530e8 (diff)
Fix typos in Documentation/filesystems/seq_file.txt
A couple of typos crept into the newly added document about the seq_file interface. This patch corrects those typos and simultaneously deletes unnecessary trailing spaces. Signed-off-by: Dmitri Vorobiev <dmitri.vorobiev@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/filesystems')
-rw-r--r--Documentation/filesystems/seq_file.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/filesystems/seq_file.txt b/Documentation/filesystems/seq_file.txt
index cc6cdb95b73a..7fb8e6dc62bf 100644
--- a/Documentation/filesystems/seq_file.txt
+++ b/Documentation/filesystems/seq_file.txt
@@ -92,7 +92,7 @@ implementations; in most cases the start() function should check for a
92"past end of file" condition and return NULL if need be. 92"past end of file" condition and return NULL if need be.
93 93
94For more complicated applications, the private field of the seq_file 94For more complicated applications, the private field of the seq_file
95structure can be used. There is also a special value whch can be returned 95structure can be used. There is also a special value which can be returned
96by the start() function called SEQ_START_TOKEN; it can be used if you wish 96by the start() function called SEQ_START_TOKEN; it can be used if you wish
97to instruct your show() function (described below) to print a header at the 97to instruct your show() function (described below) to print a header at the
98top of the output. SEQ_START_TOKEN should only be used if the offset is 98top of the output. SEQ_START_TOKEN should only be used if the offset is
@@ -146,7 +146,7 @@ the four functions we have just defined:
146This structure will be needed to tie our iterator to the /proc file in 146This structure will be needed to tie our iterator to the /proc file in
147a little bit. 147a little bit.
148 148
149It's worth noting that the interator value returned by start() and 149It's worth noting that the iterator value returned by start() and
150manipulated by the other functions is considered to be completely opaque by 150manipulated by the other functions is considered to be completely opaque by
151the seq_file code. It can thus be anything that is useful in stepping 151the seq_file code. It can thus be anything that is useful in stepping
152through the data to be output. Counters can be useful, but it could also be 152through the data to be output. Counters can be useful, but it could also be
@@ -262,7 +262,7 @@ routines useful:
262 262
263These helpers will interpret pos as a position within the list and iterate 263These helpers will interpret pos as a position within the list and iterate
264accordingly. Your start() and next() functions need only invoke the 264accordingly. Your start() and next() functions need only invoke the
265seq_list_* helpers with a pointer to the appropriate list_head structure. 265seq_list_* helpers with a pointer to the appropriate list_head structure.
266 266
267 267
268The extra-simple version 268The extra-simple version