From: Thomas Monjalon <thomas@monjalon.net>
To: Chengwen Feng <fengchengwen@huawei.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com, kevin.laatz@intel.com
Subject: Re: [PATCH 0/2] bugfix and enhance for DMA test
Date: Wed, 15 Oct 2025 12:24:31 +0200 [thread overview]
Message-ID: <2580558.CrzyxZ31qj@thomas> (raw)
In-Reply-To: <20250827012829.40752-1-fengchengwen@huawei.com>
27/08/2025 03:28, Chengwen Feng:
> This patchset contains one bugfix (some case never fail) and one
> enhance (support auto adapt ringsize).
>
> Chengwen Feng (2):
> test/dma: fix some testcase never fail
> test/dma: support auto adapt ringsize
Applied, thanks.
prev parent reply other threads:[~2025-10-15 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 1:28 Chengwen Feng
2025-08-27 1:28 ` [PATCH 1/2] test/dma: fix some testcase never fail Chengwen Feng
2025-08-27 1:28 ` [PATCH 2/2] test/dma: support auto adapt ringsize Chengwen Feng
2025-08-27 7:36 ` Bruce Richardson
2025-10-15 10:24 ` Thomas Monjalon [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=2580558.CrzyxZ31qj@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=kevin.laatz@intel.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;
as well as URLs for NNTP newsgroup(s).