1 From 012cfd55bb9075c4697cc068ba0a8c0d0069433a Mon Sep 17 00:00:00 2001
2 From: Christoph Hellwig <hch@lst.de>
3 Date: Tue, 4 Jan 2011 07:14:24 +0100
4 Subject: [PATCH 63/65] remove trim_fs method from Documentation/filesystems/Locking
6 The ->trim_fs has been removed meanwhile, so remove it from the documentation
9 Signed-off-by: Christoph Hellwig <hch@lst.de>
10 Reported-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
11 Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
13 Documentation/filesystems/Locking | 2 --
14 1 files changed, 0 insertions(+), 2 deletions(-)
16 diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking
17 index 7686e76..33fa3e5 100644
18 --- a/Documentation/filesystems/Locking
19 +++ b/Documentation/filesystems/Locking
20 @@ -115,7 +115,6 @@ prototypes:
21 ssize_t (*quota_read)(struct super_block *, int, char *, size_t, loff_t);
22 ssize_t (*quota_write)(struct super_block *, int, const char *, size_t, loff_t);
23 int (*bdev_try_to_free_page)(struct super_block*, struct page*, gfp_t);
24 - int (*trim_fs) (struct super_block *, struct fstrim_range *);
27 All may block [not true, see below]
28 @@ -138,7 +137,6 @@ show_options: no (namespace_sem)
29 quota_read: no (see below)
30 quota_write: no (see below)
31 bdev_try_to_free_page: no (see below)
34 ->statfs() has s_umount (shared) when called by ustat(2) (native or
35 compat), but that's an accident of bad API; s_umount is used to pin