From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: linux-next: manual merge of the staging tree with the block tree Date: Mon, 4 Nov 2013 21:20:10 -0800 Message-ID: <20131105052010.GA14557@kroah.com> References: <20131105160924.4da55b7e36aa2ab93443fdda@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:47041 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750775Ab3KEFR5 (ORCPT ); Tue, 5 Nov 2013 00:17:57 -0500 Content-Disposition: inline In-Reply-To: <20131105160924.4da55b7e36aa2ab93443fdda@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Kent Overstreet , Jens Axboe On Tue, Nov 05, 2013 at 04:09:24PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in > drivers/staging/lustre/lustre/llite/lloop.c between commit ed2d2f9a8265 > ("block: Abstract out bvec iterator") from the block tree and commit > de40d1209898 ("staging: lustre: fix bug with LL_MRF_RETURN in > loop_make_request") from the staging tree. > > I fixed it up (see below) and can carry the fix as necessary (no action > is required). Looks good to me, thanks. greg k-h