From: Thomas Monjalon <thomas@monjalon.net>
To: Mingxia Liu <mingxia.liu@intel.com>
Cc: web@dpdk.org, beilei.xing@intel.com
Subject: Re: [PATCH] add Intel cpfl to supported NICs
Date: Tue, 14 Mar 2023 10:47:19 +0100 [thread overview]
Message-ID: <1810569.QZUTf85G27@thomas> (raw)
In-Reply-To: <20230314020759.1445151-1-mingxia.liu@intel.com>
14/03/2023 03:07, Mingxia Liu:
> This driver is for Intel® IPU E2100 (Device ID: 0x1453).
> And this driver is added at DPDK 23.03 release.
>
> Signed-off-by: Mingxia Liu <mingxia.liu@intel.com>
> ---
> content/supported/nics/intel.md | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/content/supported/nics/intel.md b/content/supported/nics/intel.md
> index 1564d33..e4bf0c1 100644
> --- a/content/supported/nics/intel.md
> +++ b/content/supported/nics/intel.md
> @@ -1,9 +1,10 @@
> +++
> title = "Intel"
> -description = "e1000, ixgbe, i40e, ice, idpf, fm10k, ipn3ke, ifc, igc"
> +description = "cpfl, e1000, ixgbe, i40e, ice, idpf, fm10k, ipn3ke, ifc, igc"
What is the sorting here? It there a logic?
> hidden = true
> +++
>
> +- [cpfl](//doc.dpdk.org/guides/nics/cpfl.html) (IPU E2100)
> - [e1000](//doc.dpdk.org/guides/nics/e1000em.html) (82540, 82545, 82546)
> - [e1000e](//git.dpdk.org/dpdk/tree/drivers/net/e1000/) (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)
> - [igb](//doc.dpdk.org/guides/nics/igb.html) (82573, 82576, 82580, I210, I211, I350, I354, DH89xx)
>
prev parent reply other threads:[~2023-03-14 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 2:07 Mingxia Liu
2023-03-14 4:06 ` Xing, Beilei
2023-03-14 5:39 ` Liu, Mingxia
2023-03-14 17:59 ` Stephen Hemminger
2023-03-15 7:12 ` Liu, Mingxia
2023-03-14 4:40 ` [PATCH v2] " Mingxia Liu
2023-03-14 9:48 ` Thomas Monjalon
2023-03-15 6:41 ` [PATCH v3] " Mingxia Liu
2023-03-31 8:38 ` Thomas Monjalon
2023-03-14 9:47 ` 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=1810569.QZUTf85G27@thomas \
--to=thomas@monjalon.net \
--cc=beilei.xing@intel.com \
--cc=mingxia.liu@intel.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).