[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150414161841.GA8479@lst.de>
Date: Tue, 14 Apr 2015 18:18:41 +0200
From: Christoph Hellwig <hch@....de>
To: Theodore Ts'o <tytso@....edu>, Christoph Hellwig <hch@....de>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Al Viro <viro@...IV.linux.org.uk>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, Sheng Yong <shengyong1@...wei.com>
Subject: Re: linux-next: manual merge of the vfs tree with the ext4 tree
On Tue, Apr 07, 2015 at 11:26:46PM -0400, Theodore Ts'o wrote:
> On Tue, Apr 07, 2015 at 09:02:14AM +0200, Christoph Hellwig wrote:
> > FYI, the ext4 tree seems to have the crypto support, which I don't think is
> > ready for 4.1 with all the implications of it..
>
> What sort of implications are you concerned about? We're no longer
> exposing anything via the xattr interface, and all of the changes are
> not contained strictly within the ext4 tree.
>
> There are still are some cleanups which I'm still in the process of
> applying, but I considered it more likely than not something that was
> ready for 4.1, so that's why I let it go into the ext4 dev branch for
> testing in linux-next.
A far as I can tell the patches were just posted last week, and it's
still under very active review. Also for something that while only
implemented in one filesystem has pretty broad API implications I'd
really expect a generalist VFS review (I plan to get to it ASAP..).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists