From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: VFS tree for 3.17?
Date: Tue, 22 Jul 2014 09:24:55 -0700 [thread overview]
Message-ID: <20140722162455.GA15053@infradead.org> (raw)
In-Reply-To: <20140716114136.GA25237@infradead.org>
On Wed, Jul 16, 2014 at 04:41:36AM -0700, Christoph Hellwig wrote:
> Hi Al,
>
> Do you plan to put a VFS tree together for 3.17? To me the various
> renameat2 bits from Miklos are something I'd really prefer to not miss,
> but there might be other bits waiting for attention as well.
Another weeks has passed and I'd really like to make sure we don't
let the VFS leap.
I'll try to put together a tree over the next days so we can at least
get a minium amount of linux-next exposure. Candidates are:
- the direct-io.c warning fix from Boaz (really should 3.16 actually)
- the unmount on symlink reference count fix
- the rename/rename2 patches from Mikilos. These are a bit older
and could use a respin.
Anything else I've missed?
next prev parent reply other threads:[~2014-07-22 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 11:41 VFS tree for 3.17? Christoph Hellwig
2014-07-22 16:24 ` Christoph Hellwig [this message]
2014-07-22 16:47 ` Richard Weinberger
2014-07-24 15:30 ` Christoph Hellwig
2014-07-24 16:35 ` Miklos Szeredi
2014-07-26 15:03 ` Christoph Hellwig
2014-07-24 23:18 ` Stephen Rothwell
2014-07-26 15:02 ` [GIT PULL] VFS fixes for 3.16 Christoph Hellwig
2014-07-30 17:20 ` VFS tree for 3.17? J. Bruce Fields
2014-07-30 20:54 ` Christoph Hellwig
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=20140722162455.GA15053@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sfr@canb.auug.org.au \
--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 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).