From: Christoph Hellwig <hch@lst.de>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, hare@suse.de,
kbusch@kernel.org, sagi@grimberg.me, jmeneghi@redhat.com,
axboe@kernel.dk, martin.petersen@oracle.com, gjoyce@ibm.com
Subject: Re: [RFC PATCHv5 0/3] improve NVMe multipath handling
Date: Wed, 14 May 2025 17:22:44 +0200 [thread overview]
Message-ID: <20250514152244.GA32525@lst.de> (raw)
In-Reply-To: <20250514130322.393656-1-nilay@linux.ibm.com>
Thanks,
applied to nvme-6.16.
next prev parent reply other threads:[~2025-05-14 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 13:03 [RFC PATCHv5 0/3] improve NVMe multipath handling Nilay Shroff
2025-05-14 13:03 ` [RFC PATCHv5 1/3] nvme-multipath: introduce delayed removal of the multipath head node Nilay Shroff
2025-05-14 13:03 ` [RFC PATCHv5 2/3] nvme: introduce multipath_always_on module param Nilay Shroff
2025-05-14 13:03 ` [RFC PATCHv5 3/3] nvme: rename nvme_mpath_shutdown_disk to nvme_mpath_remove_disk Nilay Shroff
2025-05-14 15:22 ` Christoph Hellwig [this message]
2025-05-15 8:22 ` [RFC PATCHv5 0/3] improve NVMe multipath handling Niklas Cassel
2025-05-15 8:49 ` Nilay Shroff
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=20250514152244.GA32525@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=gjoyce@ibm.com \
--cc=hare@suse.de \
--cc=jmeneghi@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
/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