From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:52516 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1033475AbdD0CYL (ORCPT ); Wed, 26 Apr 2017 22:24:11 -0400 Date: Wed, 26 Apr 2017 22:24:08 -0400 From: Mike Snitzer To: Bart Van Assche Cc: "hch@lst.de" , "dm-devel@redhat.com" , "linux-block@vger.kernel.org" Subject: Re: small dm mpath cleanups Message-ID: <20170427022407.GA19985@redhat.com> References: <20170426074039.14602-1-hch@lst.de> <1493232084.2632.5.camel@sandisk.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1493232084.2632.5.camel@sandisk.com> Sender: linux-block-owner@vger.kernel.org List-Id: linux-block@vger.kernel.org On Wed, Apr 26 2017 at 2:41pm -0400, Bart Van Assche wrote: > On Wed, 2017-04-26 at 09:40 +0200, Christoph Hellwig wrote: > > this series has some prep patches for my work to have proper, type > > checked block errors codes. One fallout of that is that we need to > > get rid of how dm overloads a few return values with either internal > > positive error codes or negative errno values. This patches does > > that, which happens to clean things up a bit, and also allows us > > dm to propagate the actual error code in one case where it currently > > is dropped on the floor. > > Hello Christoph, > > Some patches in this series conflict with patches I would like to end up in > the stable kernel series. If I would rebase my patch series on top of your > series then that would make it harder to apply my patches on the stable > kernel trees. Mike and Christoph, please advise how to proceed. I'll go over your series and christoph's tomorrow (thursday). I'll pull all fixes to the front and rebase later patches as needed. Mike