From: Patrick Robb <probb@iol.unh.edu>
To: "Tu, Lijuan" <lijuan.tu@intel.com>
Cc: dts@dpdk.org, dvo-plv@napatech.com, aa@napatech.com,
mak-plv@napatech.com, oko-plv@napatech.com,
Aaron Conole <aconole@redhat.com>
Subject: Napatech custom DTS testsuites/testcases
Date: Thu, 20 Jul 2023 13:10:17 -0400 [thread overview]
Message-ID: <CAJvnSUA3m=yDmT0vGyyBcYHRGwSmrtV9OWeEN6WWWOp96BDaCw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
Hi Lijuan,
Napatech has developed some custom DTS testsuites/testcases for testing
their NIC and DPDK driver. They are interested in upstreaming their
testsuites to DTS, but are wondering about the release schedule. The RFC
deadline for DPDK is August 12th. They are wondering whether there is a
similar deadline for DTS, or if they can submit the patchseries upstreaming
their DTS changes at any time. Please advise.
Thanks!
--
Patrick Robb
Technical Service Manager
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
www.iol.unh.edu
[-- Attachment #2: Type: text/html, Size: 2587 bytes --]
reply other threads:[~2023-07-20 17:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJvnSUA3m=yDmT0vGyyBcYHRGwSmrtV9OWeEN6WWWOp96BDaCw@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=aa@napatech.com \
--cc=aconole@redhat.com \
--cc=dts@dpdk.org \
--cc=dvo-plv@napatech.com \
--cc=lijuan.tu@intel.com \
--cc=mak-plv@napatech.com \
--cc=oko-plv@napatech.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).