DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: DTS roadmap for 24.03
Date: Thu, 21 Dec 2023 17:01:16 +0100	[thread overview]
Message-ID: <CAOb5WZbNr8Ry-wkQgRLN-BcrvCswN7M5jMV7+t7WjEZ1DQR-sQ@mail.gmail.com> (raw)

Here are the DTS items the community plans on adding to 24.03:

Existing patches:
* Dockerfile as a convenient way for developers to use DTS:
https://patches.dpdk.org/project/dpdk/list/?series=25550
* DTS HTML API generation from DTS docstrings:
https://patches.dpdk.org/project/dpdk/list/?series=30303
* Test case blocking and logging:
https://patches.dpdk.org/project/dpdk/list/?series=30628
* Scatter test suite: https://patches.dpdk.org/project/dpdk/list/?series=30604

Items without patches:
* Packet filtering capabilities when capturing packets
* Unify licenses across the framework

Speculative items:
* New unh developers will begin writing ethdev testsuites. Some more
trivial ones may be finished in 24.03 with more following in 24.07.

Regards,
Juraj

                 reply	other threads:[~2023-12-21 16:01 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=CAOb5WZbNr8Ry-wkQgRLN-BcrvCswN7M5jMV7+t7WjEZ1DQR-sQ@mail.gmail.com \
    --to=juraj.linkes@pantheon.tech \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).