From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
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: Wed, 30 Jul 2014 13:20:09 -0400 [thread overview]
Message-ID: <20140730172008.GH26316@fieldses.org> (raw)
In-Reply-To: <20140724153057.GA1584@infradead.org>
On Thu, Jul 24, 2014 at 08:30:57AM -0700, Christoph Hellwig wrote:
> I've pushed out the current queue to:
>
> git://git.infradead.org/users/hch/vfs.git vfs-for-3.17
>
> Stephen, can you include this in linux-next for testing? I plan to
> send the first two patches to Linus on Saturday as they seems worth
> to fix for this release still, between a user triggered refcount one off
> and a fix for a just introduced warning.
>
> If there's anything else for 3.17 please send it my way.
There's these fixes to d_splice_alias and related code:
git://linux-nfs.org/~bfields/linux-topics.git for-viro
(last posted in June).
The project isn't really finished but I think those patches are
justifiable on their own.
Happy to repost.
--b.
next prev parent reply other threads:[~2014-07-30 17:20 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
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 ` J. Bruce Fields [this message]
2014-07-30 20:54 ` VFS tree for 3.17? 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=20140730172008.GH26316@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.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 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.