From: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@fb.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 2/2] nvme: create slaves/holder entries for multipath devices
Date: Thu, 6 Dec 2018 14:48:47 -0200 [thread overview]
Message-ID: <20181206164846.GF4269@calabresa> (raw)
In-Reply-To: <20181206154432.GA26584@lst.de>
On Thu, Dec 06, 2018 at 04:44:32PM +0100, Christoph Hellwig wrote:
> On Wed, Nov 28, 2018 at 06:38:17AM -0200, Thadeu Lima de Souza Cascardo wrote:
> > I will send a followup that includes your two patches, fixing up this one, plus
> > another two because that is simply reverting the revert of Hanne's patch. Which
> > means it still has the lsblk bug.
> >
> > Then, we have two options: do not use GENHD_FL_HIDDEN on multipath nvme disks,
> > or expose devt for those disks. I am sending a patch for the second option.
>
> Can you please send it out so we can look at it before the 4.21 merge
> window opens?
Just sent. Sorry about the delay.
Thanks.
Cascardo.
prev parent reply other threads:[~2018-12-06 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 13:08 provide slaves/holders links for multipath devices Christoph Hellwig
2018-11-16 13:08 ` [PATCH 1/2] block: move holder tracking from struct block_device to hd_struct Christoph Hellwig
2018-11-28 1:59 ` Sagi Grimberg
2018-11-16 13:08 ` [PATCH 2/2] nvme: create slaves/holder entries for multipath devices Christoph Hellwig
2018-11-28 1:59 ` Sagi Grimberg
2018-11-28 8:38 ` Thadeu Lima de Souza Cascardo
2018-12-06 15:44 ` Christoph Hellwig
2018-12-06 16:48 ` Thadeu Lima de Souza Cascardo [this message]
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=20181206164846.GF4269@calabresa \
--to=cascardo@canonical.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox