From: Marco Stornelli <marco.stornelli@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: [PATCH 00/22 v2] drop vmtruncate
Date: Sat, 06 Oct 2012 10:09:30 +0200 [thread overview]
Message-ID: <506FE73A.9080406@gmail.com> (raw)
Hi all,
I send the vmtruncate cleaning patches. With theses patches we remove
the now deprecated vmtruncate and ->truncate() inode operations. The
patches are now rebased against Linus tree and I add the cleaning of
documentation. Please, consider this series for merge window of 3.7.
Thanks.
Marco Stornelli (22):
ufs: drop vmtruncate
sysv: drop vmtruncate
reiserfs: drop vmtruncate
procfs: drop vmtruncate
omfs: drop vmtruncate
ocfs2: drop vmtruncate
adfs: drop vmtruncate
affs: drop vmtruncate
bfs: drop vmtruncate
hfs: drop vmtruncate
hpfs: drop vmtruncate
jfs: drop vmtruncate
hfsplus: drop vmtruncate
hostfs: drop vmtruncate
logfs: drop vmtruncate
minix: drop vmtruncate
ncpfs: drop vmtruncate
nilfs2: drop vmtruncate
ntfs: drop vmtruncate
vfs: drop vmtruncate
mm: drop vmtruncate
documentation: drop vmtruncate
Documentation/filesystems/Locking | 6 ------
Documentation/filesystems/porting | 13 +------------
Documentation/filesystems/vfs.txt | 11 -----------
fs/adfs/inode.c | 5 +++--
fs/affs/file.c | 8 +++++---
fs/affs/inode.c | 5 ++++-
fs/bfs/file.c | 5 +++--
fs/hfs/inode.c | 19 +++++++++++++------
fs/hfsplus/inode.c | 19 +++++++++++++------
fs/hostfs/hostfs_kern.c | 8 +++++---
fs/hpfs/file.c | 8 +++++---
fs/hpfs/inode.c | 5 ++++-
fs/jfs/file.c | 6 ++++--
fs/jfs/inode.c | 13 +++++++++----
fs/libfs.c | 2 --
fs/logfs/readwrite.c | 10 ++++++++--
fs/minix/file.c | 6 ++++--
fs/minix/inode.c | 7 +++++--
fs/ncpfs/inode.c | 4 +++-
fs/nilfs2/file.c | 1 -
fs/nilfs2/inode.c | 18 +++++++++++++-----
fs/nilfs2/recovery.c | 7 +++++--
fs/ntfs/file.c | 8 +++++---
fs/ntfs/inode.c | 11 +++++++++--
fs/ntfs/inode.h | 4 ++++
fs/ocfs2/file.c | 3 ++-
fs/omfs/file.c | 12 ++++++++----
fs/proc/base.c | 3 ++-
fs/proc/generic.c | 3 ++-
fs/proc/proc_sysctl.c | 3 ++-
fs/reiserfs/file.c | 3 +--
fs/reiserfs/inode.c | 15 +++++++++++----
fs/reiserfs/reiserfs.h | 1 +
fs/sysv/file.c | 5 +++--
fs/sysv/itree.c | 7 +++++--
fs/ufs/inode.c | 5 +++--
include/linux/fs.h | 1 -
include/linux/mm.h | 1 -
mm/truncate.c | 23 -----------------------
39 files changed, 165 insertions(+), 129 deletions(-)
--
1.7.3.4
---
reply other threads:[~2012-10-06 8:16 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=506FE73A.9080406@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox