From: Wei Huang <wei.huang@intel.com>
To: dev@dpdk.org, thomas@monjalon.net, david.marchand@redhat.com
Cc: stable@dpdk.org, rosen.xu@intel.com, tianfei.zhang@intel.com,
qi.z.zhang@intel.com, Wei Huang <wei.huang@intel.com>
Subject: [PATCH v1] doc/guides/nics: remove limitation of ipn3ke
Date: Wed, 22 Mar 2023 21:00:53 -0400 [thread overview]
Message-ID: <20230323010053.620258-1-wei.huang@intel.com> (raw)
Now ipn3ke is not evaluation in 19.05 .
Signed-off-by: Wei Huang <wei.huang@intel.com>
---
doc/guides/nics/ipn3ke.rst | 4 ----
1 file changed, 4 deletions(-)
diff --git a/doc/guides/nics/ipn3ke.rst b/doc/guides/nics/ipn3ke.rst
index a89e371..d269bbe 100644
--- a/doc/guides/nics/ipn3ke.rst
+++ b/doc/guides/nics/ipn3ke.rst
@@ -93,7 +93,3 @@ To start ``testpmd``, and add I40e PF to FPGA network port, enable FPGA HQoS and
Limitations or Known issues
---------------------------
-19.05 limitation
-~~~~~~~~~~~~~~~~
-
-Ipn3ke code released in 19.05 is for evaluation only.
--
1.8.3.1
next reply other threads:[~2023-03-23 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 1:00 Wei Huang [this message]
2023-03-23 8:53 ` Thomas Monjalon
2023-03-24 1:29 ` Huang, Wei
2023-03-28 16:19 ` 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=20230323010053.620258-1-wei.huang@intel.com \
--to=wei.huang@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=rosen.xu@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tianfei.zhang@intel.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).