From: Sagi Grimberg <sagi@grimberg.me>
To: Chaitanya Kulkarni <kch@nvidia.com>,
song@kernel.org, yukuai@fnnas.com, linan122@huawei.com,
kbusch@kernel.org, axboe@kernel.dk, hch@lst.de
Cc: linux-raid@vger.kernel.org, linux-nvme@lists.infradead.org,
kmodukuri@nvidia.com
Subject: Re: [PATCH V3 3/3] nvme-multipath: enable PCI P2PDMA for multipath devices
Date: Mon, 11 May 2026 00:17:10 +0300 [thread overview]
Message-ID: <e3d32d96-dbcd-4915-955c-3c63c891b5bb@grimberg.me> (raw)
In-Reply-To: <20260416212633.72650-4-kch@nvidia.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2026-05-10 21:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 21:26 [PATCH V3 0/2] md/nvme: Enable PCI P2PDMA support for RAID0 and NVMe Multipath Chaitanya Kulkarni
2026-04-16 21:26 ` [PATCH V3 1/3] block: clear BLK_FEAT_PCI_P2PDMA in blk_stack_limits() for non-supporting devices Chaitanya Kulkarni
2026-04-17 7:52 ` Christoph Hellwig
2026-04-17 10:11 ` Nitesh Shetty
2026-04-21 22:30 ` Chaitanya Kulkarni
2026-04-22 5:30 ` Nitesh Shetty
2026-04-22 6:20 ` Christoph Hellwig
2026-05-10 21:16 ` Sagi Grimberg
2026-04-16 21:26 ` [PATCH V3 2/3] md: propagate BLK_FEAT_PCI_P2PDMA from member devices to RAID device Chaitanya Kulkarni
2026-04-17 7:53 ` Christoph Hellwig
2026-04-21 9:18 ` Xiao Ni
2026-05-10 21:16 ` Sagi Grimberg
2026-04-16 21:26 ` [PATCH V3 3/3] nvme-multipath: enable PCI P2PDMA for multipath devices Chaitanya Kulkarni
2026-04-17 7:53 ` Christoph Hellwig
2026-04-17 10:42 ` Nitesh Shetty
2026-05-10 21:17 ` Sagi Grimberg [this message]
2026-04-21 22:32 ` [PATCH V3 0/2] md/nvme: Enable PCI P2PDMA support for RAID0 and NVMe Multipath Chaitanya Kulkarni
2026-04-22 6:22 ` hch
2026-05-04 21:25 ` Pranjal Shrivastava
2026-05-05 0:32 ` Chaitanya Kulkarni
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=e3d32d96-dbcd-4915-955c-3c63c891b5bb@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=kmodukuri@nvidia.com \
--cc=linan122@huawei.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=yukuai@fnnas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox