DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Yang, Qiming" <qiming.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: move i40e know issue to new file
Date: Fri, 24 Mar 2017 05:03:15 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B57E082@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1490330480-26531-1-git-send-email-qiming.yang@intel.com>

Hi Qiming,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qiming Yang
> Sent: Friday, March 24, 2017 12:41 PM
> To: dev@dpdk.org
> Cc: Wu, Jingjing; Yang, Qiming
> Subject: [dpdk-dev] [PATCH] doc: move i40e know issue to new file
> 
> This patch moved i40e related know issues from doc/guides/rel_notes/
> known_issues.rst to driver/net/i40e/i40e_know_issues.rst, makes us easy to
> track the issue about i40e.
> 
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> ---
>  doc/guides/rel_notes/known_issues.rst | 65 -----------------------------------
>  drivers/net/i40e/i40e_know_issues.rst | 54
> +++++++++++++++++++++++++++++
You create a new file for it? We already have a doc file here, doc/guides/nics/i40e.rst.

  reply	other threads:[~2017-03-24  5:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24  4:41 Qiming Yang
2017-03-24  5:03 ` Lu, Wenzhuo [this message]
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
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=6A0DE07E22DDAD4C9103DF62FEBC09093B57E082@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=qiming.yang@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).