DPDK website maintenance
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
	"web@dpdk.org" <web@dpdk.org>
Cc: nd <nd@arm.com>
Subject: RE: [PATCH] update DTS roadmap for 23.07
Date: Wed, 31 May 2023 21:20:05 +0000	[thread overview]
Message-ID: <DBAPR08MB5814560C34ED39A65AB65FDA98489@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20230531104517.2370506-1-thomas@monjalon.net>



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, May 31, 2023 5:45 AM
> To: web@dpdk.org
> Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> Subject: [PATCH] update DTS roadmap for 23.07
> 
> Was announced in the dpdk-dev mailing list:
> https://mails.dpdk.org/archives/dev/2023-May/267961.html
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Looks good.
Reviewed-by: Honnappa Nagarahalli <Honnappa.nagarahalli@arm.com>

> ---
>  content/roadmap/_index.md | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md index
> 0cdc0c9..b377893 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -58,6 +58,11 @@ This list is obviously neither complete nor guaranteed.
>  - control adapter and RX adapter enhancements in DLB driver
>  <!-- Others -->
>  - DMA performance test tool
> +- DTS automated documentation
> +- DTS integration of Fabric
> +- DTS abstraction of traffic generator
> +- DTS non-traffic smoke tests
> +- DTS Docker file
> 
>  ### Nice to have - Future {#future}
>  ----
> --
> 2.40.1


      reply	other threads:[~2023-05-31 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 10:45 Thomas Monjalon
2023-05-31 21:20 ` Honnappa Nagarahalli [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=DBAPR08MB5814560C34ED39A65AB65FDA98489@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \
    --cc=web@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).