From: "Yang, Qiming" <qiming.yang@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: move i40e know issue to new file
Date: Mon, 27 Mar 2017 01:43:46 +0000 [thread overview]
Message-ID: <F5DF4F0E3AFEF648ADC1C3C33AD4DBF16EDEAA31@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23328B36B@IRSMSX103.ger.corp.intel.com>
Hi, John
> -----Original Message-----
> From: Mcnamara, John
> Sent: Friday, March 24, 2017 10:38 PM
> To: Mcnamara, John <john.mcnamara@intel.com>; Yang, Qiming
> <qiming.yang@intel.com>; 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
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mcnamara, John
> > Sent: Friday, March 24, 2017 2:33 PM
> > To: Yang, Qiming <qiming.yang@intel.com>; 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
> >
> >
> >
> > > -----Original Message-----
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qiming Yang
> > > Sent: Friday, March 24, 2017 4:41 AM
> > > To: dev@dpdk.org
> > > Cc: Wu, Jingjing <jingjing.wu@intel.com>; Yang, Qiming
> > > <qiming.yang@intel.com>
> > > 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.
> >
> >
> > That's good. Someone should probably check if there are other cases
> > like this in the last 3-4 releases and move them as well.
> >
>
> Sorry. I missed the fact that this was going to a new, i40e, specific file.
> I don't think that is a good idea. Maybe there could be a new i40e section in
> the known issues doc but I don't think that we should introduce a new file.
>
> John
You are right, it's no need to introduce a new file, but Wenzhuo told me an exist doc doc/guides/nics/i40e.rst. What do you think to move the i40e relate known issues to this doc?
Qiming
next prev parent reply other threads:[~2017-03-27 1:43 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
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 [this message]
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=F5DF4F0E3AFEF648ADC1C3C33AD4DBF16EDEAA31@SHSMSX101.ccr.corp.intel.com \
--to=qiming.yang@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@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).