From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>,
"jspewock@iol.unh.edu" <jspewock@iol.unh.edu>,
Patrick Robb <probb@iol.unh.edu>,
Paul Szczepanek <Paul.Szczepanek@arm.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>, nd <nd@arm.com>
Subject: Re: DTS roadmap for 23.11
Date: Thu, 12 Oct 2023 08:39:06 +0200 [thread overview]
Message-ID: <CAOb5WZYWfppNy6vRjpCFX9x40Pakxoc1Kp7Bcn3dyepkWE=W=Q@mail.gmail.com> (raw)
In-Reply-To: <DBAPR08MB5814CA7DC21A928E657D48F998D3A@DBAPR08MB5814.eurprd08.prod.outlook.com>
A minor correction
On Thu, Oct 12, 2023 at 2:50 AM Honnappa Nagarahalli
<Honnappa.Nagarahalli@arm.com> wrote:
>
> Hello,
> Following is the roadmap for DTS for 23.11 release.
>
> 1) DTS API document auto generation
> https://patches.dpdk.org/project/dpdk/cover/20230831100407.59865-1-juraj.linkes@pantheon.tech/
>
> 2) Scatter test suite along with TG packet manipulation and verification
> https://patches.dpdk.org/project/dpdk/patch/20230811212929.21983-3-jspewock@iol.unh.edu/
>
> 3) Pending patches to merge
> Dockerfile for DTS - https://patches.dpdk.org/project/dpdk/patch/20221103134633.446646-1-juraj.linkes@pantheon.tech/
>
> 4) Already merged patches
> Update dependencies for Poetry: http://patches.dpdk.org/project/dpdk/patch/20230725084842.23147-1-juraj.linkes@pantheon.tech/
> Increase Python code max line length to 100: http://patches.dpdk.org/project/dpdk/patch/20230928121830.62608-1-juraj.linkes@pantheon.tech/
This max line length patch has not yet been merged, so should be under 3).
Juraj
>
> Thanks,
> Honnappa
>
>
prev parent reply other threads:[~2023-10-12 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 0:50 Honnappa Nagarahalli
2023-10-12 6:39 ` Juraj Linkeš [this message]
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='CAOb5WZYWfppNy6vRjpCFX9x40Pakxoc1Kp7Bcn3dyepkWE=W=Q@mail.gmail.com' \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=nd@arm.com \
--cc=probb@iol.unh.edu \
--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).