DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: david.marchand@redhat.com, honnappa.nagarahalli@arm.com,
	niklas.soderlund@corigine.com, liudongdong3@huawei.com,
	jerinj@marvell.com, lmargalit@nvidia.com,
	mb@smartsharesystems.com
Subject: [PATCH 0/7] 22.11 roadmaps
Date: Sun, 27 Nov 2022 21:12:38 +0100	[thread overview]
Message-ID: <20221127201245.884619-1-thomas@monjalon.net> (raw)

Better late than never!
Before cleaning up the roadmap for the release 22.11,
adding the items sent during the release.

Thomas Monjalon (7):
  update DTS roadmap for 22.11
  update Arm roadmap for 22.11
  update Corigine roadmap for 22.11
  update Huawei roadmap for 22.11
  update Marvell roadmap for 22.11
  update NVIDIA roadmap for 22.11
  update SmartShare Systems roadmap for 22.11

 content/roadmap/_index.md | 41 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

-- 
2.36.1


             reply	other threads:[~2022-11-27 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 20:12 Thomas Monjalon [this message]
2022-11-27 20:12 ` [PATCH 1/7] update DTS roadmap for 22.11 Thomas Monjalon
2022-11-27 20:12 ` [PATCH 2/7] update Arm " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 3/7] update Corigine " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 4/7] update Huawei " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 5/7] update Marvell " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 6/7] update NVIDIA " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 7/7] update SmartShare Systems " Thomas Monjalon
2022-11-27 20:43   ` Morten Brørup
2022-11-27 21:34     ` Thomas Monjalon

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=20221127201245.884619-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=liudongdong3@huawei.com \
    --cc=lmargalit@nvidia.com \
    --cc=mb@smartsharesystems.com \
    --cc=niklas.soderlund@corigine.com \
    --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).