From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Jeremy Spewock" <jspewock@iol.unh.edu>,
"Patrick Robb" <probb@iol.unh.edu>,
"Lincoln Lavoie" <lylavoie@iol.unh.edu>,
"Lijuan Tu" <lijuan.tu@intel.com>,
"Ruifeng Wang" <Ruifeng.Wang@arm.com>,
"Wathsala Wathawana Vithanage" <wathsala.vithanage@arm.com>,
nd <nd@arm.com>, nd <nd@arm.com>
Subject: DTS roadmap for 23.07 release
Date: Mon, 15 May 2023 21:33:52 +0000 [thread overview]
Message-ID: <DBAPR08MB5814DF1059F7788C61E599F798789@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
Hello,
Following is the roadmap for DTS for 23.07 release.
1) Tooling for developing automated documentation for DTS API docs. Uses Google docstring format.
Link: http://patches.dpdk.org/project/dpdk/cover/20230511091408.236638-1-juraj.linkes@pantheon.tech/
2) Integrate Fabric. This will contain the support for sudo with no password, removing use of scp.
Link: http://patches.dpdk.org/project/dpdk/patch/20230424133537.58698-1-juraj.linkes@pantheon.tech/
3) Traffic Generator abstraction
http://patches.dpdk.org/project/dpdk/cover/20230420093109.594704-1-juraj.linkes@pantheon.tech/
3) Non traffic based smoke tests
http://patches.dpdk.org/project/dpdk/cover/20230413175415.7683-2-jspewock@iol.unh.edu/
4) Minor changes:
a) Using a git commit ID instead of tarball.
Link: http://patches.dpdk.org/project/dpdk/patch/20230420140244.701467-1-juraj.linkes@pantheon.tech/
b) Updates to the linter tools.
Link: http://patches.dpdk.org/project/dpdk/patch/20230331091355.1224059-1-juraj.linkes@pantheon.tech/
5) Docker file for build and run environment
Link: http://patches.dpdk.org/project/dpdk/patch/20221103134633.446646-1-juraj.linkes@pantheon.tech/
Thank you,
Honnappa
reply other threads:[~2023-05-15 21:34 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=DBAPR08MB5814DF1059F7788C61E599F798789@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@intel.com \
--cc=lylavoie@iol.unh.edu \
--cc=nd@arm.com \
--cc=probb@iol.unh.edu \
--cc=wathsala.vithanage@arm.com \
/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).