From: Theodore Ts'o <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: dhowells@redhat.com, viro@ZenIV.linux.org.uk,
Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>,
jaegeuk@kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH 0/5] Miklos's vfs/nfs/ext4 patches in the ext4.git tree
Date: Sat, 26 Mar 2016 17:09:55 -0400 [thread overview]
Message-ID: <1459026600-9232-1-git-send-email-tytso@mit.edu> (raw)
I have the following patches in the ext4.git tree which I plan to push
to Linus as bug fixes during this development cycles. Al, are you
happy with Miklos's v2 version of "fs: add file_dentrY()" patch?
Miklos Szeredi (4):
fs: add file_dentry()
nfs: use file_dentry()
ext4: use dget_parent() in ext4_file_open()
ext4: use file_dentry()
Theodore Ts'o (1):
ext4 crypto: use dget_parent() in ext4_d_revalidate()
fs/dcache.c | 5 ++++-
fs/ext4/crypto.c | 12 ++++++++----
fs/ext4/file.c | 12 ++++++++----
fs/nfs/dir.c | 6 +++---
fs/nfs/inode.c | 2 +-
fs/nfs/nfs4file.c | 4 ++--
fs/overlayfs/super.c | 33 +++++++++++++++++++++++++++++++++
include/linux/dcache.h | 10 ++++++++++
include/linux/fs.h | 10 ++++++++++
9 files changed, 79 insertions(+), 15 deletions(-)
--
2.5.0
next reply other threads:[~2016-03-26 21:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 21:09 Theodore Ts'o [this message]
2016-03-26 21:09 ` [PATCH 1/5] fs: add file_dentry() Theodore Ts'o
2016-03-26 21:09 ` [PATCH 2/5] nfs: use file_dentry() Theodore Ts'o
2016-03-26 21:09 ` [PATCH 3/5] ext4: use dget_parent() in ext4_file_open() Theodore Ts'o
2016-03-26 21:09 ` [PATCH 4/5] ext4: use file_dentry() Theodore Ts'o
2016-03-26 21:10 ` [PATCH 5/5] ext4 crypto: use dget_parent() in ext4_d_revalidate() Theodore Ts'o
2016-03-27 8:02 ` Sedat Dilek
2016-03-27 18:16 ` Theodore Ts'o
2016-03-27 8:06 ` [PATCH 0/5] Miklos's vfs/nfs/ext4 patches in the ext4.git tree Sedat Dilek
2016-03-27 18:15 ` Theodore Ts'o
2016-03-27 19:31 ` Sedat Dilek
2016-03-28 12:36 ` Theodore Ts'o
2016-03-27 22:51 ` Sedat Dilek
2016-03-28 14:02 ` Chris Mason
2016-03-29 17:15 ` Theodore Ts'o
2016-03-29 20:12 ` Chris Mason
2016-03-29 19:58 ` Al Viro
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=1459026600-9232-1-git-send-email-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=dhowells@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).