DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org, harini.ramakrishnan@microsoft.com
Cc: eilong@mellanox.com, pallavi.kadam@intel.com,
	ranjit.menon@intel.com, ocardona@microsoft.com,
	shshaikh@marvell.com, nareshkumar.pbs@broadcom.com,
	ravianan@cisco.com, talshn@mellanox.com, hgani@marvell.com,
	rksaripa@cisco.com, narcisa.vasile@microsoft.com,
	dmitry.kozliuk@gmail.com, u9012063@gmail.com,
	ophirmu@mellanox.com, thasreef@chelsio.com
Subject: Re: [dpdk-web] [PATCH] add roadmap for Windows
Date: Tue, 25 Feb 2020 10:16:38 +0100	[thread overview]
Message-ID: <2873348.U7HbjWM52l@xps> (raw)
In-Reply-To: <20200219212602.2332159-1-thomas@monjalon.net>

19/02/2020 22:26, Thomas Monjalon:
> Initial DPDK PMD support is planned for LTS release 20.11.
> 
> Broadcom, Chelsio, Cisco, Intel, Marvell, Mellanox, Microsoft,
> and all volunteers are welcomed joining this effort.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> 
> This page will appear at http://core.dpdk.org/roadmap/windows/
> If no comment by the end of this week, it will be published.
> 
> Please do not hesitate to suggest rewords or additions,
> especially for vendor-specific steps for a PMD.

Applied

This is the first revision of the roadmap.
Please send any update or addition as a patch.

Few details of Mellanox milestones are shared.
Would be good to have such milestones for other PMDs.




      reply	other threads:[~2020-02-25  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 21:26 Thomas Monjalon
2020-02-25  9:16 ` Thomas Monjalon [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=2873348.U7HbjWM52l@xps \
    --to=thomas@monjalon.net \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=eilong@mellanox.com \
    --cc=harini.ramakrishnan@microsoft.com \
    --cc=hgani@marvell.com \
    --cc=narcisa.vasile@microsoft.com \
    --cc=nareshkumar.pbs@broadcom.com \
    --cc=ocardona@microsoft.com \
    --cc=ophirmu@mellanox.com \
    --cc=pallavi.kadam@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=ravianan@cisco.com \
    --cc=rksaripa@cisco.com \
    --cc=shshaikh@marvell.com \
    --cc=talshn@mellanox.com \
    --cc=thasreef@chelsio.com \
    --cc=u9012063@gmail.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).