From: Randy Dunlap <rdunlap@xenotime.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Marcos Paulo de Souza <marcos.mage@gmail.com>
Subject: [PATCH 3/8] Documentation: fix inotify source file paths
Date: Fri, 04 Nov 2011 11:22:14 -0700 [thread overview]
Message-ID: <4EB42D56.8070503@xenotime.net> (raw)
In-Reply-To: <4EB423D8.9030102@xenotime.net>
From: Marcos Paulo de Souza <marcos.mage@gmail.com>
Fixes the path to find the source files of the inotify subsystem.
Signed-off-by: Marcos Paulo de Souza <marcos.mage@gmail.com>
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
Documentation/filesystems/inotify.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- lnx1104.orig/Documentation/filesystems/inotify.txt
+++ lnx1104/Documentation/filesystems/inotify.txt
@@ -194,7 +194,8 @@ associated with the inotify_handle, and
Each watch is associated with an inotify_watch structure. Watches are chained
off of each associated inotify_handle and each associated inode.
-See fs/inotify.c and fs/inotify_user.c for the locking and lifetime rules.
+See fs/notify/inotify/inotify_fsnotify.c and fs/notify/inotify/inotify_user.c
+for the locking and lifetime rules.
(vi) Rationale
next prev parent reply other threads:[~2011-11-04 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EB423D8.9030102@xenotime.net>
2011-11-04 18:22 ` [PATCH 2/8] Documentation: thinkpad-acpi grammo fixes Randy Dunlap
2011-11-04 18:22 ` Randy Dunlap [this message]
2011-11-04 18:22 ` [PATCH 4/8] Documentation: update CodingStyle use of braces Randy Dunlap
2011-11-04 18:22 ` [PATCH 5/8] Documentation: HFS is orphaned Randy Dunlap
2011-11-04 18:22 ` [PATCH 6/8] Documentation: Computone ip2 " Randy Dunlap
2011-11-04 18:22 ` [PATCH 7/8] Documentation: fix leds-class.txt duplicated word Randy Dunlap
2011-11-04 18:22 ` [PATCH 8/8] Documentation: drop as block elevator reference in switching-sched.txt Randy Dunlap
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=4EB42D56.8070503@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.mage@gmail.com \
--cc=torvalds@linux-foundation.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