From 3b39be566da8e21e4b6adc8c7f194b98897744a4 Mon Sep 17 00:00:00 2001 From: Marcelo Tosatti Date: Fri, 16 Sep 2005 19:28:01 -0700 Subject: [PATCH] --- yaml --- r: 9029 b: refs/heads/master c: afeda2c24e74cbddde376e06fdd82c215f9cb637 h: refs/heads/master i: 9027: 0ed065dc22a9bb4c5c36a6fd9d5b2e06f4704647 v: v3 --- [refs] | 2 +- trunk/Documentation/filesystems/relayfs.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 4c2973281c68..359438bcd4d2 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 514ccd4e6c414d8064d53235f7fc09fc02ec2078 +refs/heads/master: afeda2c24e74cbddde376e06fdd82c215f9cb637 diff --git a/trunk/Documentation/filesystems/relayfs.txt b/trunk/Documentation/filesystems/relayfs.txt index d24e1b0d4f39..d803abed29f0 100644 --- a/trunk/Documentation/filesystems/relayfs.txt +++ b/trunk/Documentation/filesystems/relayfs.txt @@ -15,7 +15,7 @@ retrieve the data as it becomes available. The format of the data logged into the channel buffers is completely up to the relayfs client; relayfs does however provide hooks which -allow clients to impose some stucture on the buffer data. Nor does +allow clients to impose some structure on the buffer data. Nor does relayfs implement any form of data filtering - this also is left to the client. The purpose is to keep relayfs as simple as possible.