From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH v3 0/5] clean-up NICs list and add Aquantia
Date: Wed, 21 Nov 2018 01:11:12 +0100 [thread overview]
Message-ID: <20181121001117.24537-1-thomas@monjalon.net> (raw)
In-Reply-To: <a1a283344a8816a92a2efd019418c82841e3f755.1541239202.git.igor.russkikh@aquantia.com>
When trying to add a new vendor (Aquantia) to the NICs list,
it has been discussed to sort by name instead of renumbering weights.
This v3 is doing more cleanups and fix the messed output of the list.
Igor Russkikh (1):
add Aquantia devices to supported NICs
Thomas Monjalon (4):
remove useless metadata
rename NICs directory
simplify NICs list
add driver names in NICs list
content/_index.md | 4 ++--
content/supported/_index.md | 3 ++-
content/supported/nics/_index.md | 4 ++++
content/supported/{NICs => nics}/amazon.md | 4 +---
content/supported/nics/aquantia.md | 7 +++++++
content/supported/{NICs => nics}/atomicrules.md | 4 +---
content/supported/{NICs => nics}/broadcom.md | 4 +---
content/supported/{NICs => nics}/cavium.md | 4 +---
content/supported/{NICs => nics}/chelsio.md | 4 +---
content/supported/{NICs => nics}/cisco.md | 4 +---
content/supported/{NICs => nics}/intel.md | 4 +---
content/supported/{NICs => nics}/marvell.md | 4 +---
content/supported/{NICs => nics}/mellanox.md | 4 +---
content/supported/{NICs => nics}/netcope.md | 4 +---
content/supported/{NICs => nics}/netronome.md | 4 +---
content/supported/{NICs => nics}/nxp.md | 4 +---
content/supported/{NICs => nics}/solarflare.md | 4 +---
content/supported/others.md | 5 ++---
content/supported/paravirtualization.md | 3 +--
19 files changed, 31 insertions(+), 47 deletions(-)
create mode 100644 content/supported/nics/_index.md
rename content/supported/{NICs => nics}/amazon.md (70%)
create mode 100644 content/supported/nics/aquantia.md
rename content/supported/{NICs => nics}/atomicrules.md (73%)
rename content/supported/{NICs => nics}/broadcom.md (73%)
rename content/supported/{NICs => nics}/cavium.md (88%)
rename content/supported/{NICs => nics}/chelsio.md (72%)
rename content/supported/{NICs => nics}/cisco.md (71%)
rename content/supported/{NICs => nics}/intel.md (93%)
rename content/supported/{NICs => nics}/marvell.md (80%)
rename content/supported/{NICs => nics}/mellanox.md (82%)
rename content/supported/{NICs => nics}/netcope.md (71%)
rename content/supported/{NICs => nics}/netronome.md (69%)
rename content/supported/{NICs => nics}/nxp.md (80%)
rename content/supported/{NICs => nics}/solarflare.md (73%)
--
2.19.0
next prev parent reply other threads:[~2018-11-21 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 10:14 [dpdk-web] [PATCH v2] add aquantia devices to the list of supported nics Igor Russkikh
2018-11-21 0:11 ` Thomas Monjalon [this message]
2018-11-21 0:11 ` [dpdk-web] [PATCH v3 1/5] remove useless metadata Thomas Monjalon
2018-11-21 0:11 ` [dpdk-web] [PATCH v3 2/5] rename NICs directory Thomas Monjalon
2018-11-21 0:11 ` [dpdk-web] [PATCH v3 3/5] simplify NICs list Thomas Monjalon
2018-11-21 0:11 ` [dpdk-web] [PATCH v3 4/5] add driver names in " Thomas Monjalon
2018-11-21 0:11 ` [dpdk-web] [PATCH v3 5/5] add Aquantia devices to supported NICs Thomas Monjalon
2018-11-22 13:55 ` [dpdk-web] [PATCH v3 0/5] clean-up NICs list and add Aquantia Thomas Monjalon
2018-11-22 14:38 ` Ferruh Yigit
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=20181121001117.24537-1-thomas@monjalon.net \
--to=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).