DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	 Qiming Yang <qiming.yang@intel.com>
Cc: web@dpdk.org, Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
Subject: Re: [dpdk-web] [PATCH v2] add XXV710 to i40e suppported NICs
Date: Thu, 28 Jun 2018 17:45:42 +0100	[thread overview]
Message-ID: <d0e035e4-ffdc-326a-e17d-79715e9047a7@intel.com> (raw)
In-Reply-To: <3194454.J7243SyqOs@xps>

On 5/29/2018 9:00 AM, Thomas Monjalon wrote:
> 29/05/2018 04:19, Wenzhuo Lu:
>> From: Qiming Yang <qiming.yang@intel.com>
>>
>> XXV710 is pre-enabled on v16.11 and be validated on v17.02.
>>
>> Reference commit: 75d133dd32963c6897f97077c270082f1b4fef4e
>>
>> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> 
> Applied, thanks

Hi Thomas,

I can't see this information (XXV710 as supported NIC) in the web page, it may
be lost somehow, how can we add it back?


And supported hardware information is presented in two different location in
webpage:
https://core.dpdk.org/supported/
https://www.dpdk.org/ecosystem/#hardware

Can we reduce it into single place?
Is ecosystem good place for listing hardware support?


And as last, formatting of multiple device listing is not good, it is almost not
readable for Intel ones on https://core.dpdk.org/supported/, how can we fix it?


Thanks,
ferruh

  reply	other threads:[~2018-06-28 16:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16  2:32 [dpdk-web] [PATCH] " Wenzhuo Lu
2018-05-16  5:50 ` Zhang, Helin
2018-05-16  8:26 ` Mcnamara, John
2018-05-17 13:20 ` Thomas Monjalon
2018-05-29  2:19 ` [dpdk-web] [PATCH v2] " Wenzhuo Lu
2018-05-29  8:00   ` Thomas Monjalon
2018-06-28 16:45     ` Ferruh Yigit [this message]
2018-06-28 20:11       ` [dpdk-web] supported hardware list Thomas Monjalon
2018-07-02 10:32         ` Ferruh Yigit
2018-08-21 11:15           ` Ferruh Yigit
2018-08-21 11:23             ` Trishan de Lanerolle
2018-08-21 11:31               ` Ferruh Yigit
2018-09-03  7:56                 ` 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=d0e035e4-ffdc-326a-e17d-79715e9047a7@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    --cc=wenzhuo.lu@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).