From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "Brandon Lo" <blo@iol.unh.edu>,
"Ashwin Sekhar Thalakalath Kottilveetil" <asekhar@marvell.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Owen Hilyard" <ohilyard@iol.unh.edu>, dev <dev@dpdk.org>
Cc: nd <nd@arm.com>, nd <nd@arm.com>
Subject: [dpdk-dev] DTS Workgroup: MoM 05/26/2021
Date: Wed, 2 Jun 2021 06:17:11 +0000 [thread overview]
Message-ID: <DBAPR08MB5814B0C4505A0EEBEF50D3B0983D9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
Attendees:
Ashwin Shekar
Brandon Lo
Honnappa Nagarahalli
Lijuan Tu
Juraj Linkes
Owen Hilyard
The meeting announcements are sent to dev@dpdk.org.
Minutes:
Review action items from 5/19/2021
1) Test-pmd investigation under progress. Patch does not apply with git. Need to use 'patch' command.
2) DTS master is merged to dts-next (Thanks Lijuan)
3) Compiling the list is under progress. The excel sheet will capture the test cases along with the classes, diff if possible. This work is getting captured at [2]
4) DTS Bugzilla to fix the IAVF enablement in the framework is created [3], Lijuan will get the ticket fixed.
5) LF has added a link on DTS bugs in the DTS links under hosted projects
6) The work item related discussions are captured in [1]
[1] https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit?usp=sharing
[2] https://docs.google.com/spreadsheets/d/1i7x4ecPiRXNKOrOy0the5WyGSWbdMxPLK7aWbuWI4ew/edit#gid=880561943
[3] https://bugs.dpdk.org/show_bug.cgi?id=715
reply other threads:[~2021-06-02 6:17 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=DBAPR08MB5814B0C4505A0EEBEF50D3B0983D9@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=asekhar@marvell.com \
--cc=blo@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@intel.com \
--cc=nd@arm.com \
--cc=ohilyard@iol.unh.edu \
/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).