From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@lst.de" <hch@lst.de>, "snitzer@redhat.com" <snitzer@redhat.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: small dm mpath cleanups
Date: Wed, 26 Apr 2017 18:41:27 +0000 [thread overview]
Message-ID: <1493232084.2632.5.camel@sandisk.com> (raw)
In-Reply-To: <20170426074039.14602-1-hch@lst.de>
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.
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@lst.de" <hch@lst.de>, "snitzer@redhat.com" <snitzer@redhat.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: small dm mpath cleanups
Date: Wed, 26 Apr 2017 18:41:27 +0000 [thread overview]
Message-ID: <1493232084.2632.5.camel@sandisk.com> (raw)
In-Reply-To: <20170426074039.14602-1-hch@lst.de>
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.
Bart.=
next prev parent reply other threads:[~2017-04-26 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 7:40 small dm mpath cleanups Christoph Hellwig
2017-04-26 7:40 ` [PATCH 1/4] dm mpath: merge do_end_io into multipath_end_io Christoph Hellwig
2017-04-26 7:40 ` [PATCH 2/4] dm rq: change ->rq_end_io calling conventions Christoph Hellwig
2017-04-26 7:40 ` [PATCH 3/4] dm mpath: simplify multipath_clone_and_map a little bit Christoph Hellwig
2017-04-26 7:40 ` [PATCH 4/4] dm: introduce a new DM_MAPIO_KILL return value Christoph Hellwig
2017-04-26 18:41 ` Bart Van Assche [this message]
2017-04-26 18:41 ` small dm mpath cleanups Bart Van Assche
2017-04-27 2:24 ` Mike Snitzer
2017-04-27 6:33 ` hch
2017-04-28 20:23 ` Mike Snitzer
2017-04-28 20:42 ` Bart Van Assche
2017-04-28 20:42 ` Bart Van Assche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1493232084.2632.5.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=snitzer@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.