From: lijuan.tu@intel.com
To: dts@dpdk.org,Wei Ling <weix.ling@intel.com>
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V2 3/3] tests/basic_4k_pages_cbdma: add basic_4k_pages_cbdma testsuite
Date: 04 May 2022 22:37:10 -0700 [thread overview]
Message-ID: <003cea$he13km@orsmga008-auth.jf.intel.com> (raw)
In-Reply-To: <20220429075736.21043-1-weix.ling@intel.com>
On Fri, 29 Apr 2022 07:57:36 +0000, Wei Ling <weix.ling@intel.com> wrote:
> As commit 53d3f4778c(vhost: integrate dmadev in asynchronous data-path),
> add new testsuite basic_4k_pages_cbdma for coverage the pvp
> virtio-user 4k pages with cbdma.
> 1) Add new testsuite TestSuite_basic_4k_pages_cbdma.py into tests.
>
> Signed-off-by: Wei Ling <weix.ling@intel.com>
Series applied, thanks
next prev parent reply other threads:[~2022-05-05 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 7:57 Wei Ling
2022-04-29 8:46 ` Huang, ChenyuX
2022-05-05 5:37 ` lijuan.tu [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-29 7:02 Wei Ling
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='003cea$he13km@orsmga008-auth.jf.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=weix.ling@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).