aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/relay.txt
diff options
context:
space:
mode:
authorMatt LaPlante <kernel1@cyberdogtech.com>2007-05-09 01:35:06 -0400
committerAdrian Bunk <bunk@stusta.de>2007-05-09 02:58:15 -0400
commita982ac06b069f6ee9ea1b64f4ce68cdf2e138742 (patch)
treefb120a416db15d09722e8780b7a09d0da1a9b94e /Documentation/filesystems/relay.txt
parent148e423f909e14564d8af13239c5d060f7df273e (diff)
misc doc and kconfig typos
Fix various typos in kernel docs and Kconfigs, 2.6.21-rc4. Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/filesystems/relay.txt')
-rw-r--r--Documentation/filesystems/relay.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/filesystems/relay.txt b/Documentation/filesystems/relay.txt
index 7fbb6ffe5769..18d23f9a18c7 100644
--- a/Documentation/filesystems/relay.txt
+++ b/Documentation/filesystems/relay.txt
@@ -351,7 +351,7 @@ If the current buffer is full, i.e. all sub-buffers remain unconsumed,
351the callback returns 0 to indicate that the buffer switch should not 351the callback returns 0 to indicate that the buffer switch should not
352occur yet, i.e. until the consumer has had a chance to read the 352occur yet, i.e. until the consumer has had a chance to read the
353current set of ready sub-buffers. For the relay_buf_full() function 353current set of ready sub-buffers. For the relay_buf_full() function
354to make sense, the consumer is reponsible for notifying the relay 354to make sense, the consumer is responsible for notifying the relay
355interface when sub-buffers have been consumed via 355interface when sub-buffers have been consumed via
356relay_subbufs_consumed(). Any subsequent attempts to write into the 356relay_subbufs_consumed(). Any subsequent attempts to write into the
357buffer will again invoke the subbuf_start() callback with the same 357buffer will again invoke the subbuf_start() callback with the same