From: Nitesh Shetty <nj.shetty@samsung.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
nitheshshetty@gmail.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/2] nvme: blk_rq_dma_map_iter_next is no longer using iova state
Date: Mon, 12 Jan 2026 19:58:22 +0530 [thread overview]
Message-ID: <20260112142822.tk34ei4evgypw3qv@green245.gost> (raw)
In-Reply-To: <5b07dbce-2644-4079-a768-9167cbe3e25a@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On 12/01/26 03:08PM, Damien Le Moal wrote:
>On 1/12/26 14:57, Nitesh Shetty wrote:
>> DMA IOVA state is not used inside blk_rq_dma_map_iter_next
>>
>> Signed-off-by: Nitesh Shetty <nj.shetty@samsung.com>
>> ---
>> drivers/nvme/host/pci.c | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
>> index 3b528369f5454..065555576d2f9 100644
>> --- a/drivers/nvme/host/pci.c
>> +++ b/drivers/nvme/host/pci.c
>> @@ -823,7 +823,7 @@ static bool nvme_pci_prp_iter_next(struct request *req, struct device *dma_dev,
>>
>> if (iter->len)
>> return true;
>> - if (!blk_rq_dma_map_iter_next(req, dma_dev, &iod->dma_state, iter))
>> + if (!blk_rq_dma_map_iter_next(req, dma_dev, iter))
>
>Hu... Why is this not squashed with the previous patch ? If only patch 1 is
>applied, this will not compile, right ?
>
I couldn’t decide whether to use the layering convention or a unified patch,
so I chose one patch per layer.
Agreed, independently this doesn't compile, merging make sense.
I will resend.
Thanks,
Nitesh
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2026-01-12 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260112140159epcas5p35303b39d11d8379b8527026e72bf0f40@epcas5p3.samsung.com>
2026-01-12 13:57 ` [PATCH 1/2] block: remove unused dma_iova_state function parameter Nitesh Shetty
[not found] ` <CGME20260112140208epcas5p4c3ef0209b01be379c836f705a10efa7d@epcas5p4.samsung.com>
2026-01-12 13:57 ` [PATCH 2/2] nvme: blk_rq_dma_map_iter_next is no longer using iova state Nitesh Shetty
2026-01-12 14:08 ` Damien Le Moal
2026-01-12 14:28 ` Nitesh Shetty [this message]
2026-01-13 7:24 ` Christoph Hellwig
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=20260112142822.tk34ei4evgypw3qv@green245.gost \
--to=nj.shetty@samsung.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nitheshshetty@gmail.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
all inboxes | Powered by JetHome®