[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100601081823.GA29991@infradead.org>
Date: Tue, 1 Jun 2010 04:18:23 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Philipp Reisner <philipp.reisner@...bit.com>, drbd-dev@...bit.com,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Julia Lawall <julia@...u.dk>,
Al Viro <viro@...iv.linux.org.uk>,
Jens Axboe <jens.axboe@...cle.com>
Subject: Re: linux-next: manual merge of the drbd tree with Linus' tree
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?
--
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