Messages in this thread Patch in this message | | | From | Radu Voicilas <> | Subject | [PATCH] fsnotify_backend.h: Fixed spelling mistakes. | Date | Fri, 21 Jan 2011 15:12:52 +0200 |
| |
Whilst going through fsnotify's internals I came up over some trivial spelling mistakes that got fixed with this patch.
Signed-off-by: Radu Voicilas <rvoicilas@gmail.com> --- include/linux/fsnotify_backend.h | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/fsnotify_backend.h b/include/linux/fsnotify_backend.h index 69ad89b..5e34383 100644 --- a/include/linux/fsnotify_backend.h +++ b/include/linux/fsnotify_backend.h @@ -19,7 +19,7 @@ #include <asm/atomic.h> /* - * IN_* from inotfy.h lines up EXACTLY with FS_*, this is so we can easily + * IN_* from inotify.h lines up EXACTLY with FS_*, this is so we can easily * convert between them. dnotify only needs conversion at watch creation * so no perf loss there. fanotify isn't defined yet, so it can use the * wholes if it needs more events. @@ -55,7 +55,7 @@ * dnotify and inotify. */ #define FS_EVENT_ON_CHILD 0x08000000 -/* This is a list of all events that may get sent to a parernt based on fs event +/* This is a list of all events that may get sent to a parent based on fs event * happening to inodes inside that directory */ #define FS_EVENTS_POSS_ON_CHILD (FS_ACCESS | FS_MODIFY | FS_ATTRIB |\ FS_CLOSE_WRITE | FS_CLOSE_NOWRITE | FS_OPEN |\ @@ -81,7 +81,7 @@ struct fsnotify_mark; struct fsnotify_event_private_data; /* - * Each group much define these ops. The fsnotify infrastructure will call + * Each group must define these ops. The fsnotify infrastructure will call * these operations for each relevant group. * * should_send_event - given a group, inode, and mask this function determines -- 1.7.0
| |