From: Jeff Layton <jlayton@kernel.org>
To: akpm@linux-foundation.org
Cc: lustre-devel@lists.lustre.org, anton@tuxera.com,
andreas.dilger@intel.com, oleg.drokin@intel.com,
jsimmons@infradead.org, mikulas@artax.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: [RESEND][PATCH 0/3] fs: remove unnecessary i_version handling from various filesystems
Date: Thu, 7 Dec 2017 06:32:03 -0500 [thread overview]
Message-ID: <20171207113206.31544-1-jlayton@kernel.org> (raw)
From: Jeff Layton <jlayton@redhat.com>
Hi Andrew,
I sent these patches to the various fs maintainers prior to the last
merge window, but they didn't get picked up. This is mainly removing
i_version/f_version handling from filesystems that don't implement it
properly, and that don't use it anyway.
This is almost certainly the result of cargo-cult copying from other
filesystems.
Would you be willing to merge these for the v4.16 window?
Thanks,
Jeff
Jeff Layton (3):
lustre: don't set f_version in ll_readdir
ntfs: remove i_version handling
hpfs: don't bother with the i_version counter or f_version
drivers/staging/lustre/lustre/llite/dir.c | 3 ---
fs/hpfs/dir.c | 1 -
fs/hpfs/dnode.c | 2 --
fs/hpfs/super.c | 1 -
fs/ntfs/inode.c | 9 ---------
fs/ntfs/mft.c | 6 ------
6 files changed, 22 deletions(-)
--
2.14.3
next reply other threads:[~2017-12-07 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 11:32 Jeff Layton [this message]
2017-12-07 11:32 ` [RESEND][PATCH 1/3] lustre: don't set f_version in ll_readdir Jeff Layton
2017-12-07 11:32 ` [RESEND][PATCH 2/3] ntfs: remove i_version handling Jeff Layton
2017-12-07 11:32 ` [RESEND][PATCH 3/3] hpfs: don't bother with the i_version counter or f_version Jeff Layton
2017-12-07 11:40 ` [RESEND][PATCH 0/3] fs: remove unnecessary i_version handling from various filesystems Anton Altaparmakov
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=20171207113206.31544-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andreas.dilger@intel.com \
--cc=anton@tuxera.com \
--cc=jsimmons@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=lustre-devel@lists.lustre.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=oleg.drokin@intel.com \
/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.