DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Qiu <michael.qiu@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2 v2] fm10k: update doc for Atwood Channel
Date: Thu,  4 Feb 2016 16:36:06 +0800	[thread overview]
Message-ID: <1454574966-31124-2-git-send-email-michael.qiu@intel.com> (raw)
In-Reply-To: <1454574966-31124-1-git-send-email-michael.qiu@intel.com>

Atwood Channel is 25GbE NIC and belongs to Intel FM10K family,
update the doc for it.

Signed-off-by: Michael Qiu <michael.qiu@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
---
Change log:
   1. modify 20GbE to 25GbE 

 doc/guides/rel_notes/release_2_3.rst | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/guides/rel_notes/release_2_3.rst b/doc/guides/rel_notes/release_2_3.rst
index 99de186..7dd9c0f 100644
--- a/doc/guides/rel_notes/release_2_3.rst
+++ b/doc/guides/rel_notes/release_2_3.rst
@@ -3,7 +3,9 @@ DPDK Release 2.3
 
 New Features
 ------------
+* **New NIC Atwood Channel support.**
 
+  Added support for the Atwood Channel variant of Intel's fm10k NIC family.
 
 Resolved Issues
 ---------------
-- 
1.9.3

  reply	other threads:[~2016-02-04  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11  7:28 [dpdk-dev] [PATCH 1/2] fm10k: Add Atwood Channel Support Michael Qiu
2016-01-11  7:28 ` [dpdk-dev] [PATCH 2/2] fm10k: update doc for Atwood Channel Michael Qiu
2016-01-12 13:31   ` Mcnamara, John
2016-02-03  7:25   ` Chen, Jing D
2016-01-12 13:31 ` [dpdk-dev] [PATCH 1/2] fm10k: Add Atwood Channel Support Mcnamara, John
2016-02-04  8:36 ` [dpdk-dev] [PATCH 1/2 v2] " Michael Qiu
2016-02-04  8:36   ` Michael Qiu [this message]
2016-02-04  9:03     ` [dpdk-dev] [PATCH 2/2 v2] fm10k: update doc for Atwood Channel Thomas Monjalon
2016-02-05  5:04       ` Qiu, Michael
2016-02-04  8:40   ` [dpdk-dev] [PATCH 1/2 v2] fm10k: Add Atwood Channel Support Chen, Jing D
2016-02-04 13:55   ` Liu, Yong
2016-03-09  8:56   ` Qiu, Michael

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=1454574966-31124-2-git-send-email-michael.qiu@intel.com \
    --to=michael.qiu@intel.com \
    --cc=dev@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).