From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: Minutes of DPDK Technical Board Meeting, 2025-07-23
Date: Mon, 11 Aug 2025 14:56:17 +0200 [thread overview]
Message-ID: <2515820.jE0xQCEvom@thomas> (raw)
Members Attending: 5/11
- Aaron Conole
- Bruce Richardson
- Jerin Jacob
- Stephen Hemminger
- Thomas Monjalon (Chair)
NOTE: The Technical Board meetings take place every second Wednesday at 3 pm UTC
on https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d808f1f6-0a28-4165-929e-5a5bcae7efeb
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
The next meeting will happen on September 3.
1/ Socket and NUMA node IDs
Sometimes it is defined as a signed type, sometimes as an unsigned type.
The value -1 (SOCKET_ID_ANY) means any socket/node.
We could use a typedef to ensure consistency.
If an unsigned type is defined, we need to explicitly cast -1 value.
Defining a type would be an API breaking change but not too big,
so it could be acceptable in 25.11.
2/ DTS maintainers
Paul Szczepanek (Arm) is replaced by Luca Vizzarro (Arm)
3/ DPDK Summit
Cancellation of September Summit (California) has been announced.
https://mails.dpdk.org/archives/announce/2025-July/000536.html
4/ AI review bots
Grout repository on GitHub is already testing 2 bots (CodeRabbit and Sourcery).
For the DPDK repository, we must open a GitHub pull request for each patch series received on the mailing list.
The the review link would be published in patchwork as a test result.
We must guess the branch to use, by using the same script as for patchwork delegation.
We must check that the free versions of the AI bots accept using multiple branches.
We must decide whether to use the OVS robot account or the main DPDK account.
reply other threads:[~2025-08-11 12:56 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=2515820.jE0xQCEvom@thomas \
--to=thomas@monjalon.net \
--cc=dev@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).