From: Christoph Hellwig <hch@lst.de>
To: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: [PATCH] remove trim_fs method from Documentation/filesystems/Locking
Date: Tue, 4 Jan 2011 07:14:24 +0100 [thread overview]
Message-ID: <20110104061424.GA16112@lst.de> (raw)
In-Reply-To: <20110104.145627.180311923.ryusuke@osrg.net>
The ->trim_fs has been removed meanwhile, so remove it from the documentation
as well.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reported-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Index: linux-2.6/Documentation/filesystems/Locking
===================================================================
--- linux-2.6.orig/Documentation/filesystems/Locking 2011-01-04 07:08:41.296003372 +0100
+++ linux-2.6/Documentation/filesystems/Locking 2011-01-04 07:08:45.561004280 +0100
@@ -115,7 +115,6 @@ prototypes:
ssize_t (*quota_read)(struct super_block *, int, char *, size_t, loff_t);
ssize_t (*quota_write)(struct super_block *, int, const char *, size_t, loff_t);
int (*bdev_try_to_free_page)(struct super_block*, struct page*, gfp_t);
- int (*trim_fs) (struct super_block *, struct fstrim_range *);
locking rules:
All may block [not true, see below]
@@ -138,7 +137,6 @@ show_options: no (namespace_sem)
quota_read: no (see below)
quota_write: no (see below)
bdev_try_to_free_page: no (see below)
-trim_fs: no
->statfs() has s_umount (shared) when called by ustat(2) (native or
compat), but that's an accident of bad API; s_umount is used to pin
prev parent reply other threads:[~2011-01-04 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 17:07 [PATCH for-2.6.37] update Documentation/filesystems/Locking Christoph Hellwig
2010-12-16 11:04 ` [PATCH for-2.6.37 v2] " Christoph Hellwig
2011-01-04 5:56 ` Ryusuke Konishi
2011-01-04 6:04 ` Ryusuke Konishi
2011-01-04 6:14 ` Christoph Hellwig [this message]
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=20110104061424.GA16112@lst.de \
--to=hch@lst.de \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.