From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org, dts@dpdk.org
Subject: DTS WG Meeting Minutes - June 20, 2024
Date: Thu, 20 Jun 2024 12:32:23 -0400 [thread overview]
Message-ID: <CAJvnSUBRTBpAu7KcfOu7KX6YOzF-y1uSndfrO877xr1Zqsny1A@mail.gmail.com> (raw)
#####################################################################
Attendees
* Patrick Robb
* Juraj Linkeš
* Paul Szczepanek
* Jeremy Spewock
* Nicholas Pratte
* Dean Marx
* Luca Vizzarro
#####################################################################
Minutes
=====================================================================
General Announcements
* Thomas has merged some patchseries:
* Testpmd params:
https://patchwork.dpdk.org/project/dpdk/list/?series=32231&state=*
* Mypy: https://patchwork.dpdk.org/project/dpdk/list/?series=32026&state=*
* UNH can roll out the CI testing for mypy early next week
* Error and usage improvements:
https://patchwork.dpdk.org/project/dpdk/list/?series=32038&state=*
* Testpmd show port info/stats:
https://patchwork.dpdk.org/project/dpdk/list/?series=32112&state=*
* Rename execution to test run:
https://patchwork.dpdk.org/project/dpdk/patch/20240607083858.58906-1-juraj.linkes@pantheon.tech/
* Node and inheritance improvements:
https://patchwork.dpdk.org/project/dpdk/list/?series=32230&state=*
* Hugepage configuration refactor:
https://patchwork.dpdk.org/project/dpdk/list/?series=32129&state=*
* Thomas found an issue with Nick's patchset, some parts were
not in the right patches; the parts are in DPDK docs and each
individual commit must be valid, which was not the case with Nick's
patch
* Each individual patch must build docs successfully. The
renaming needs to be grouped into one patch instead of split out.
* Lines must be broken logically, like after a dot or comma.
But, there is a line limitation and this may restrict our ability to
write freely. There isn’t a hard requirement that the line breaks with
some punctuation (although this is helpful), a logical separation in
the sentence structure is fine too.
* Improved interactive shell output gathering not merged as there
were some unresolved comments
* Everyone please rebase
* DPDK Summit Montreal
* Possible CFP topics for DTS:
* How to write a testsuite. This could be a simple lightning
talk which shows how we wrote one of the testsuites we are working on
now.
* Luca is interested in giving this talk
* Thomas mentioned: We may discuss creating a git tree for you (for DTS)
* This would help Juraj and the DTS group have more control over
merging patches
* This is like next-* branches on DPDK. So it would be like a next-dts.
* Patrick Robbcan also add it to the agenda.
* Juraj should join to share his thoughts as DTS maintainer
* Meeting info here: https://core.dpdk.org/techboard/
* Do we want to switch to Ubuntu 24.04 as the distro of choice? This
would prompt a Python update, which we could use for dataclasses
(@typing.dataclass_transform) and other things
* RC2 should be 2 weeks out. 5th of July.
=====================================================================
Patch discussions
* Improve interactive shell output gathering/logging
* There are some unresolved comments from Nick
=====================================================================
Bugzilla discussions
* Vlan filter ethdev bug added: https://bugs.dpdk.org/show_bug.cgi?id=1464
=====================================================================
Any other business
* Next meeting Jul 3, 2024
next reply other threads:[~2024-06-20 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 16:32 Patrick Robb [this message]
2024-06-21 7:00 ` David Marchand
2024-06-25 19:31 ` Patrick Robb
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=CAJvnSUBRTBpAu7KcfOu7KX6YOzF-y1uSndfrO877xr1Zqsny1A@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
/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).