From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: ci@dpdk.org, dts@dpdk.org
Subject: DTS WG Meeting Minutes - October 10, 2024
Date: Wed, 23 Oct 2024 02:01:34 -0400 [thread overview]
Message-ID: <CAJvnSUCMvmEyUANH9VhFVfnB5cHGFpMFxD1+CdkFGBrdMRiwwQ@mail.gmail.com> (raw)
#####################################################################
October 10, 2024
Attendees
* Patrick Robb
* Paul Szczepanek
* Luca Vizzarro
#####################################################################
Minutes
=====================================================================
General Discussion
* Next-dts repo: Patrick tried to push the series “dts: add VLAN
methods to testpmd shell” to next-dts but had a permission error.
Emailing Thomas to figure out why.
* Remote needs to be updated to the correct protocol (is https
currently, that was the issue)
* TG driver binding:
https://git.dpdk.org/next/dpdk-next-dts/commit/?id=8c0722bb3bc0507745998db37fb99a38ad852a4f
* I think this is not properly adjusting for the TG setting. If TG
== SCAPY, then we should bind to the os_driver, not os_driver_for_DPDK
(what is happening currently), so I think this is a bug and I’ll make
a ticket
* Dts-format-check: There is a patch on the dpdk-ci project now which
Aaron will have to merge for us to start using this
* Manit is also going to add a patch for the create_series_artifact.py
* 24.11 roadmap status:
https://docs.google.com/document/d/1doTZOOpkv4D5P2w6K7fEJpa_CjzrlMl3mCeDBWtxnko/edit
=====================================================================
Patch discussions
* Remove os UDP test case: Luca mentioned he has some concerns which
need to be addressed first.
* Pydantic: Nick is going through a review for this series.
=====================================================================
Bugzilla discussions
* None
=====================================================================
Any other business
* Next meeting Oct 25, 2024
reply other threads:[~2024-10-23 6:03 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=CAJvnSUCMvmEyUANH9VhFVfnB5cHGFpMFxD1+CdkFGBrdMRiwwQ@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).