aboutsummaryrefslogtreecommitdiffstats
path: root/fs/inotify.c
diff options
context:
space:
mode:
authorC. Scott Ananian <cscott@laptop.org>2007-07-15 23:41:13 -0700
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-16 09:05:48 -0700
commit6b86e854f71600c809536502a0efa9d4e384fb23 (patch)
tree25696d6d1aa803547c525f90345bca85d5cc3ed2 /fs/inotify.c
parentf4895925976977aaeda26ee2a603a99f17db500b (diff)
downloadkernel_samsung_crespo-6b86e854f71600c809536502a0efa9d4e384fb23.zip
kernel_samsung_crespo-6b86e854f71600c809536502a0efa9d4e384fb23.tar.gz
kernel_samsung_crespo-6b86e854f71600c809536502a0efa9d4e384fb23.tar.bz2
update procfs-guide doc of read_func
The procfs-guide claims that 'the parameter start doesn't seem to be used anywhere in the kernel'. This is out of date. In linux/fs/proc/generic.c we find a very nice description of the parameters to read_func. The appended patch replaces the bogus description with this (as far as I know) accurate one. Cc: "Randy.Dunlap" <rdunlap@xenotime.net> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/inotify.c')
0 files changed, 0 insertions, 0 deletions