From: Qinxin Xia <xiaqinxin@huawei.com>
To: Barry Song <21cnbao@gmail.com>
Cc: <jonathan.cameron@huawei.com>, <wangzhou1@hisilicon.com>,
<iommu@lists.linux.dev>, <prime.zeng@huawei.com>,
<fanghao11@huawei.com>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>
Subject: Re: [PATCH v5 1/3] dma-mapping: benchmark: modify the framework to adapt to more map modes
Date: Tue, 23 Dec 2025 11:25:43 +0800 [thread overview]
Message-ID: <6833038b-7338-458f-92f3-67eb6faf1a03@huawei.com> (raw)
In-Reply-To: <294a3819-d850-4d90-8112-da9a21a6acf1@huawei.com>
On 2025/12/23 11:13:32, Qinxin Xia <xiaqinxin@huawei.com> wrote:
>
>
> On 2025/12/23 10:58:28, Barry Song <21cnbao@gmail.com> wrote:
>> I’ve reviewed it many times. You are:
>>
>> + if (!mb_ops->prepare_data)
>> + mb_ops->prepare_data(mparam);
>>
>> not
>> if (mb_ops->prepare_data)
>> mb_ops->prepare_data(mparam);
>> Am I crazy?
>>
>> Thanks
>> Barry
> Yes, I've found the mistake...
>
> So in my just reply, I mentioned the correct modification of the
> "if (mb_ops->prepare_data)" and suggested that if you want to test it
> before the next version, you can modify the patch in this way.
>
> Sorry for the confusion
>
if (!mb_ops->prepare_data) is a bug. Thank you for catching it.
I've tested the correct version and it works.
--
Thanks,
Qinxin
next prev parent reply other threads:[~2025-12-23 3:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 15:32 [PATCH v5 0/3] dma-mapping: benchmark: Add support for dma_map_sg Qinxin Xia
2025-12-22 15:32 ` [PATCH v5 1/3] dma-mapping: benchmark: modify the framework to adapt to more map modes Qinxin Xia
2025-12-22 21:03 ` Barry Song
2025-12-23 2:51 ` Qinxin Xia
2025-12-23 2:58 ` Barry Song
2025-12-23 3:13 ` Qinxin Xia
2025-12-23 3:25 ` Qinxin Xia [this message]
2025-12-23 3:12 ` Barry Song
2025-12-22 15:32 ` [PATCH v5 2/3] dma-mapping: benchmark: add support for dma_map_sg Qinxin Xia
2025-12-22 21:12 ` Barry Song
2025-12-22 15:32 ` [PATCH v5 3/3] tools/dma: Add dma_map_sg support Qinxin Xia
2025-12-22 21:10 ` Barry Song
2025-12-23 3:14 ` Qinxin Xia
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=6833038b-7338-458f-92f3-67eb6faf1a03@huawei.com \
--to=xiaqinxin@huawei.com \
--cc=21cnbao@gmail.com \
--cc=fanghao11@huawei.com \
--cc=iommu@lists.linux.dev \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@huawei.com \
--cc=wangzhou1@hisilicon.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
all inboxes | Powered by JetHome®