From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <keith.busch@intel.com>
Cc: Linux Block <linux-block@vger.kernel.org>,
Linux NVMe <linux-nvme@lists.infradead.org>,
Device Mapper <dm-devel@redhat.com>,
Christoph Hellwig <hch@lst.de>, Mike Snitzer <snitzer@redhat.com>,
Jens Axboe <axboe@kernel.dk>,
Bart VanAssche <bart.vanassche@wdc.com>,
James Smart <james.smart@broadcom.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.com>, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCHv2 0/5] nvme/dm failover unification
Date: Wed, 10 Jan 2018 09:28:35 +0100 [thread overview]
Message-ID: <20180110082835.GA10185@lst.de> (raw)
In-Reply-To: <20180109190418.7123-1-keith.busch@intel.com>
The whole series looks fine to me:
Reviewed-by: Christoph Hellwig <hch@lst.de>
Jens, do you want me to apply this to the nvme tree, or pick it up
directly?
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCHv2 0/5] nvme/dm failover unification
Date: Wed, 10 Jan 2018 09:28:35 +0100 [thread overview]
Message-ID: <20180110082835.GA10185@lst.de> (raw)
In-Reply-To: <20180109190418.7123-1-keith.busch@intel.com>
The whole series looks fine to me:
Reviewed-by: Christoph Hellwig <hch at lst.de>
Jens, do you want me to apply this to the nvme tree, or pick it up
directly?
next prev parent reply other threads:[~2018-01-10 8:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 19:04 [PATCHv2 0/5] nvme/dm failover unification Keith Busch
2018-01-09 19:04 ` Keith Busch
2018-01-09 19:04 ` [PATCHv2 1/5] nvme: Add more command status translation Keith Busch
2018-01-09 19:04 ` Keith Busch
2018-01-10 7:58 ` [dm-devel] " Johannes Thumshirn
2018-01-10 7:58 ` Johannes Thumshirn
2018-01-10 7:58 ` Johannes Thumshirn
2018-01-09 19:04 ` [PATCHv2 2/5] nvme/multipath: Consult blk_status_t for failover Keith Busch
2018-01-09 19:04 ` Keith Busch
2018-01-10 8:02 ` [dm-devel] " Johannes Thumshirn
2018-01-10 8:02 ` Johannes Thumshirn
2018-01-10 8:02 ` Johannes Thumshirn
2018-01-09 19:04 ` [PATCHv2 3/5] block: Provide blk_status_t decoding for path errors Keith Busch
2018-01-09 19:04 ` Keith Busch
2018-01-10 8:06 ` [dm-devel] " Johannes Thumshirn
2018-01-10 8:06 ` Johannes Thumshirn
2018-01-10 8:06 ` Johannes Thumshirn
2018-01-09 19:04 ` [PATCHv2 4/5] nvme/multipath: Use blk_path_error Keith Busch
2018-01-09 19:04 ` Keith Busch
2018-01-10 8:06 ` [dm-devel] " Johannes Thumshirn
2018-01-10 8:06 ` Johannes Thumshirn
2018-01-10 8:06 ` Johannes Thumshirn
2018-01-09 19:04 ` [PATCHv2 5/5] dm mpath: " Keith Busch
2018-01-09 19:04 ` Keith Busch
2018-01-10 8:07 ` [dm-devel] " Johannes Thumshirn
2018-01-10 8:07 ` Johannes Thumshirn
2018-01-10 8:07 ` Johannes Thumshirn
2018-01-10 8:28 ` Christoph Hellwig [this message]
2018-01-10 8:28 ` [PATCHv2 0/5] nvme/dm failover unification Christoph Hellwig
2018-01-10 17:52 ` Jens Axboe
2018-01-10 17:52 ` Jens Axboe
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=20180110082835.GA10185@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.com \
--cc=james.smart@broadcom.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
--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.