DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "Yang, Qiming" <qiming.yang@intel.com>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
Date: Wed, 21 Mar 2018 10:21:24 +0100	[thread overview]
Message-ID: <5636546.NRJykgjs9r@xps> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23EEFE384@IRSMSX103.ger.corp.intel.com>

21/03/2018 10:18, Mcnamara, John:
> 
> > -----Original Message-----
> > From: web [mailto:web-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Wednesday, March 21, 2018 8:30 AM
> > To: Yang, Qiming <qiming.yang@intel.com>
> > Cc: web@dpdk.org
> > Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
> > 
> > 21/03/2018 15:31, Qiming Yang:
> > > -				<li><a href="/doc/guides/nics/i40e.html">i40e</a>
> > (X710, XL710, X722)</li>
> > > +				<li><a href="/doc/guides/nics/i40e.html">i40e</a>
> > (X710, XL710, X722, XXV710)</li>
> > 
> > Please, could add in the message which release is supporting this device?
> 
> 
> Just to clarify, you mean to add the release in the commit message not the html, right?

Yes, just for the history, and for justification.

  reply	other threads:[~2018-03-21  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 14:31 Qiming Yang
2018-03-21  8:29 ` Thomas Monjalon
2018-03-21  9:18   ` Mcnamara, John
2018-03-21  9:21     ` Thomas Monjalon [this message]
2018-03-21  9:26       ` Mcnamara, John
2018-03-21  9:14 ` Mcnamara, John
  -- strict thread matches above, loose matches on Subject: below --
2018-05-16  9:51 Qiming Yang
2018-05-17 13:15 ` Thomas Monjalon
2018-05-28 21:14   ` Thomas Monjalon
2018-05-16  2:32 Wenzhuo Lu
2018-05-16  5:50 ` Zhang, Helin
2018-05-16  8:26 ` Mcnamara, John
2018-05-17 13:20 ` Thomas Monjalon
2018-03-21 14:25 Qiming Yang
2018-03-21 10:24 Qiming Yang

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=5636546.NRJykgjs9r@xps \
    --to=thomas@monjalon.net \
    --cc=john.mcnamara@intel.com \
    --cc=qiming.yang@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).