From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752904AbbDGHCT (ORCPT ); Tue, 7 Apr 2015 03:02:19 -0400 Received: from verein.lst.de ([213.95.11.211]:56873 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751028AbbDGHCQ (ORCPT ); Tue, 7 Apr 2015 03:02:16 -0400 Date: Tue, 7 Apr 2015 09:02:14 +0200 From: Christoph Hellwig To: Stephen Rothwell Cc: Al Viro , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Sheng Yong , Christoph Hellwig , "Theodore Ts'o" Subject: Re: linux-next: manual merge of the vfs tree with the ext4 tree Message-ID: <20150407070214.GA7074@lst.de> References: <20150407140035.60d2053d@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150407140035.60d2053d@canb.auug.org.au> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 07, 2015 at 02:00:35PM +1000, Stephen Rothwell wrote: > Hi Al, > > Today's linux-next merge of the vfs tree got a conflict in fs/ext4/inode.c between commit 72b8e0f9fa8a ("ext4: remove unused header files") from the ext4 tree and commit e2e40f2c1ed4 ("fs: move struct kiocb to fs.h") from the vfs tree. 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..