From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: "web@dpdk.org" <web@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
Shreyansh Jain <shreyansh.jain@nxp.com>,
Gagandeep Singh <G.Singh@nxp.com>
Subject: [dpdk-web] [PATCH v3] update NXP NICs and add newly supported device
Date: Fri, 23 Nov 2018 08:53:37 +0000 [thread overview]
Message-ID: <20181123085248.4716-1-shreyansh.jain@nxp.com> (raw)
In-Reply-To: <20181122103136.20194-1-shreyansh.jain@nxp.com>
Signed-off-by: Gagandeep Singh <G.Singh@nxp.com>
Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
---
v2->v3:
rebased over e24d8a8e9f7
content/supported/nics/nxp.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/content/supported/nics/nxp.md b/content/supported/nics/nxp.md
index 3f54dae..d927718 100644
--- a/content/supported/nics/nxp.md
+++ b/content/supported/nics/nxp.md
@@ -1,8 +1,9 @@
+++
title = "NXP"
-description = "dpaa, dpaa2"
+description = "dpaa, dpaa2, enetc"
hidden = true
+++
-- [dpaa](http://doc.dpdk.org/guides/nics/dpaa.html) (LS102x, LS1043, LS1046)
-- [dpaa2](http://doc.dpdk.org/guides/nics/dpaa2.html) (LS1048, LS108x, LS20xx, LX216x)
+- [dpaa](http://doc.dpdk.org/guides/nics/dpaa.html) (LS1023, LS1043, LS1046)
+- [dpaa2](http://doc.dpdk.org/guides/nics/dpaa2.html) (LS1048, LS1088, LS2084, LS2080, LS2088, LX2080, LX2160, LX2120)
+- [enetc](http://doc.dpdk.org/guides/nics/enetc.html) (LS1028)
--
2.17.1
next prev parent reply other threads:[~2018-11-23 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 10:32 [dpdk-web] [PATCH v2] " Shreyansh Jain
2018-11-22 10:34 ` Thomas Monjalon
2018-11-22 11:15 ` Shreyansh Jain
2018-11-22 11:39 ` Thomas Monjalon
2018-11-22 12:29 ` Shreyansh Jain
2018-11-22 13:58 ` Thomas Monjalon
2018-11-23 8:53 ` Shreyansh Jain [this message]
2018-11-23 9:50 ` [dpdk-web] [PATCH v3] " 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=20181123085248.4716-1-shreyansh.jain@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=G.Singh@nxp.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).