From: "Liu, Mingxia" <mingxia.liu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"web@dpdk.org" <web@dpdk.org>
Subject: RE: [PATCH] add Intel cpfl to supported NICs
Date: Wed, 15 Mar 2023 07:12:53 +0000 [thread overview]
Message-ID: <PH0PR11MB587765E0160CDA316CBB4616ECBF9@PH0PR11MB5877.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230314105930.7d394765@hermes.local>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Wednesday, March 15, 2023 2:00 AM
> To: Liu, Mingxia <mingxia.liu@intel.com>
> Cc: Xing, Beilei <beilei.xing@intel.com>; thomas@monjalon.net;
> web@dpdk.org
> Subject: Re: [PATCH] add Intel cpfl to supported NICs
>
> On Tue, 14 Mar 2023 05:39:43 +0000
> "Liu, Mingxia" <mingxia.liu@intel.com> wrote:
>
> > > > -description = "e1000, ixgbe, i40e, ice, idpf, fm10k, ipn3ke, ifc, igc"
> > > > +description = "cpfl, e1000, ixgbe, i40e, ice, idpf, fm10k, ipn3ke, ifc,
> igc"
> > >
> > > It's better to add cpfl after idpf.
> > >
> > [Liu, Mingxia] ok, v2 sent.
>
> Alphabetic sort would make more sense to user.
> Current order seems to be based on Intel release date.
[Liu, Mingxia] I will update them to alphabetic sort.
next prev parent reply other threads:[~2023-03-15 7:13 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 [this message]
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 ` [PATCH] " 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=PH0PR11MB587765E0160CDA316CBB4616ECBF9@PH0PR11MB5877.namprd11.prod.outlook.com \
--to=mingxia.liu@intel.com \
--cc=beilei.xing@intel.com \
--cc=stephen@networkplumber.org \
--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).