From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qiming Yang <qiming.yang@intel.com>, dev@dpdk.org
Cc: jingjing.wu@intel.com, john.mcnamara@intel.com, wenzhuo.lu@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: relocate i40e known issues
Date: Thu, 13 Apr 2017 11:13:51 +0100 [thread overview]
Message-ID: <d607e0a0-15bb-1270-1642-aa0c76549863@intel.com> (raw)
In-Reply-To: <1490668136-46758-1-git-send-email-qiming.yang@intel.com>
On 3/28/2017 3:28 AM, Qiming Yang wrote:
> This patch moved i40e related known issues from doc/guides/rel_notes/
> known_issues.rst to doc/guides/nics/i40e.rst, makes us easy
> to track the issue about i40e.
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> ---
> doc/guides/nics/i40e.rst | 26 ++++++++++++++
> doc/guides/rel_notes/known_issues.rst | 65 -----------------------------------
Instead of moving from "known_issues.rst" to "i40e.rst",
does it make sense to create a sub-section in "known_issues.rst" for
I40E and move these items under that sub-section,
and give a link in "i40e.rst" to that section?
next prev parent reply other threads:[~2017-04-13 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 4:41 [dpdk-dev] [PATCH] doc: move i40e know issue to new file Qiming Yang
2017-03-24 5:03 ` Lu, Wenzhuo
2017-03-27 1:23 ` Yang, Qiming
2017-03-24 14:33 ` Mcnamara, John
2017-03-24 14:38 ` Mcnamara, John
2017-03-27 1:43 ` Yang, Qiming
2017-03-27 10:29 ` Mcnamara, John
2017-03-28 2:28 ` [dpdk-dev] [PATCH v2] doc: relocate i40e known issues Qiming Yang
2017-03-30 12:06 ` Wu, Jingjing
2017-04-13 10:13 ` Ferruh Yigit [this message]
2017-04-18 5:48 ` Yang, Qiming
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=d607e0a0-15bb-1270-1642-aa0c76549863@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qiming.yang@intel.com \
--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).