mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Radu Voicilas <rvoicilas@gmail.com>
To: eparis@redhat.com
Cc: linux-kernel@vger.kernel.org, Radu Voicilas <rvoicilas@gmail.com>
Subject: [PATCH] fsnotify_backend.h: Fixed spelling mistakes.
Date: Fri, 21 Jan 2011 15:12:52 +0200	[thread overview]
Message-ID: <1295615572-18596-1-git-send-email-rvoicilas@gmail.com> (raw)

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


                 reply	other threads:[~2011-01-21 13:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1295615572-18596-1-git-send-email-rvoicilas@gmail.com \
    --to=rvoicilas@gmail.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®