From: Theodore Ts'o <tytso@mit.edu>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Goldwyn Rodrigues <rgoldwyn@suse.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
stable@vger.kernel.org, Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH 1/4] vfs: add file_dentry()
Date: Thu, 17 Mar 2016 10:18:33 -0400 [thread overview]
Message-ID: <20160317141833.GJ23593@thunk.org> (raw)
In-Reply-To: <CA+icZUWvXw0K5PgrEcf_cJdJ_=TNWLSKSHpaej3QvwT2KukNmA@mail.gmail.com>
On Thu, Mar 17, 2016 at 11:15:26AM +0100, Sedat Dilek wrote:
>
> Is that correct the ext4-related patches 3/4 and 4/4 are Linux-v4.5 material?
> Not applicable fpr v4.4.y-stable?
4.5 has already been released, but I think these patches are suitable
for the v4.[345].y-stable branch (which I think is the question you
are really asking).
Al, are you willing to push all of these to Linus before the merge
window closes, with a cc to stable@vger.kernel.org? Or I can push
them to linus via the ext4.git tree if I get signoffs/acked-by's from
the VFS and NFS maintainers.
I'll want to do a full a regression test cycle since we're pushing
patches created after the merge window opened, but I consider these
bug fixes and will certainly support pushing them to Linus as far as
ext4 is concerned.
Cheers,
- Ted
next prev parent reply other threads:[~2016-03-17 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 9:02 [PATCH 1/4] vfs: add file_dentry() Miklos Szeredi
2016-03-17 9:02 ` [PATCH 2/4] nfs: use file_dentry() Miklos Szeredi
2016-03-17 9:02 ` [PATCH 3/4] ext4: use dget_parent() in ext4_file_open() Miklos Szeredi
2016-03-17 9:02 ` [PATCH 4/4] ext4: use file_dentry() Miklos Szeredi
2016-03-17 9:09 ` [PATCH 1/4] vfs: add file_dentry() Sedat Dilek
2016-03-17 9:33 ` Miklos Szeredi
2016-03-17 10:15 ` Sedat Dilek
2016-03-17 10:19 ` Sedat Dilek
2016-03-17 14:18 ` Theodore Ts'o [this message]
2016-03-21 5:02 ` Theodore Ts'o
2016-03-21 5:22 ` Al Viro
2016-03-22 6:24 ` Daniel Axtens
2016-03-21 5:28 ` Al Viro
2016-03-21 8:16 ` Miklos Szeredi
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=20160317141833.GJ23593@thunk.org \
--to=tytso@mit.edu \
--cc=dhowells@redhat.com \
--cc=dja@axtens.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=rgoldwyn@suse.com \
--cc=sedat.dilek@gmail.com \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--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).