From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 1 Jun 2010 04:18:23 -0400 From: Christoph Hellwig To: Stephen Rothwell Message-ID: <20100601081823.GA29991@infradead.org> References: <20100601141324.edf41f7f.sfr@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100601141324.edf41f7f.sfr@canb.auug.org.au> Cc: linux-kernel@vger.kernel.org, Philipp Reisner , linux-next@vger.kernel.org, Julia Lawall , Al Viro , Jens Axboe , drbd-dev@lists.linbit.com Subject: Re: [Drbd-dev] linux-next: manual merge of the drbd tree with Linus' tree List-Id: Coordination of development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Jun 01, 2010 at 02:13:24PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the drbd tree got a conflict in fs/pipe.c > between commit cc967be54710d97c05229b2e5ba2d00df84ddd64 ("fs: Add missing > mutex_unlock") from Linus' tree and commits > 0191f8697bbdfefcd36e7b8dc3eeddfe82893e4b ("pipe: F_SETPIPE_SZ should > return -EPERM for non-root") and b9598db3401282bb27b4aef77e3eee12015f7f29 > ("pipe: make F_{GET,SET}PIPE_SZ deal with byte sizes") from the drbd tree. > > I fixed it up (see below) and can carry the fix for a while. Why is the drbd tree touching fs/pipe.c anyway?