DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Zhang, Helin" <helin.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add queue region feature info to release notes
Date: Fri, 19 Jan 2018 03:38:04 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07C99E7B@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <5680512.hVgF8YlmN2@xps>

Commit second time to cc  stable@dpdk.org
https://dpdk.org/dev/patchwork/patch/34065/

> -----Original Message-----
> From: Zhao1, Wei
> Sent: Friday, January 19, 2018 11:15 AM
> To: 'Thomas Monjalon' <thomas@monjalon.net>
> Cc: Zhang, Helin <helin.zhang@intel.com>; dev@dpdk.org; Mcnamara, John
> <john.mcnamara@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; Xing,
> Beilei <beilei.xing@intel.com>
> Subject: RE: [dpdk-dev] [PATCH v3] doc: add queue region feature info to
> release notes
> 
> Hi,  Thomas
>     Thank you! After discussion with Beilei, I have commit a new patch v4.
>  https://dpdk.org/dev/patchwork/patch/33956/
> Beilei also commit another new patch, we are waiting for review by
> Mcnamara, John.
> Do you think this is ok?
> 
> 
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Thursday, January 18, 2018 3:30 PM
> > To: Zhao1, Wei <wei.zhao1@intel.com>
> > Cc: Zhang, Helin <helin.zhang@intel.com>; dev@dpdk.org; Mcnamara,
> John
> > <john.mcnamara@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>;
> > Xing, Beilei <beilei.xing@intel.com>
> > Subject: Re: [dpdk-dev] [PATCH v3] doc: add queue region feature info
> > to release notes
> >
> > You can probably work with Beilei who is trying to do the same thing
> > for other i40e features:
> > 	https://dpdk.org/dev/patchwork/patch/33953/
> >
> >
> > 18/01/2018 03:00, Zhao1, Wei:
> > > Hi,  Thomas
> > >    I will update it in 17.11 release nots later as your comment.
> > > And it has been CC to John,  but not get any feedback.
> > >
> > > Thanks.
> > >
> > > > -----Original Message-----
> > > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > > Sent: Wednesday, January 17, 2018 5:53 AM
> > > > To: Zhang, Helin <helin.zhang@intel.com>; Zhao1, Wei
> > > > <wei.zhao1@intel.com>
> > > > Cc: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; Yigit,
> > > > Ferruh <ferruh.yigit@intel.com>
> > > > Subject: Re: [dpdk-dev] [PATCH v3] doc: add queue region feature
> > > > info to release notes
> > > >
> > > > > > > This patch add inforation about i40e queue region realted to
> > > > > > > release notes, it has been missed before in v17.11 release notes.
> > > > > > > This feature has been implemented in v17.11.
> > > > > > >
> > > > > > > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> > > > > > Acked-by: Helin Zhang <helin.zhang@intel.com>
> > > > > Applied to dpdk-next-net-intel, with minor changes. Thanks!
> > > >
> > > > This patch has not been reviewed by John, doc maintainer.
> > > > There are some english errors.
> > > > It documents extensively a testpmd addition, which is usually not
> > > > documented in release notes.
> > > > And it is adding 17.11 features in 18.02 release notes.
> > > >
> > > > It is too much, so it is just removed when pulling next-net.
> > > >
> > > > If you want to explain what is possible with i40e, you should
> > > > document it in i40e.rst.
> > > > The release notes is just a short list of what is added.
> >
> >

  parent reply	other threads:[~2018-01-19  3:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21  3:52 [dpdk-dev] [PATCH] " Wei Zhao
2017-12-21 18:10 ` Ferruh Yigit
2017-12-22  1:36   ` Zhao1, Wei
2017-12-22  3:25     ` Ferruh Yigit
2017-12-22  3:52       ` Zhao1, Wei
2018-01-16 11:27   ` Thomas Monjalon
2018-01-16 11:49     ` Ferruh Yigit
2018-01-16 16:01       ` Ferruh Yigit
2018-01-16 17:35         ` Thomas Monjalon
2018-01-03  8:13 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-01-07 15:51   ` Zhang, Helin
2018-01-08  1:56     ` Zhao1, Wei
2018-01-08  3:39   ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-01-09  6:15     ` Zhang, Helin
2018-01-09  6:17     ` Zhang, Helin
2018-01-09  6:18       ` Zhao1, Wei
2018-01-09  6:26     ` Zhang, Helin
2018-01-09  6:29     ` Zhang, Helin
2018-01-16 21:53       ` Thomas Monjalon
2018-01-18  2:00         ` Zhao1, Wei
2018-01-18  7:30           ` Thomas Monjalon
2018-01-19  3:15             ` Zhao1, Wei
2018-01-19  9:13               ` Thomas Monjalon
2018-01-19  9:17                 ` Thomas Monjalon
2018-01-22  1:58                   ` Zhao1, Wei
2018-01-22  5:30                   ` Zhao1, Wei
2018-01-19  3:38             ` Zhao1, Wei [this message]
2018-01-18  3:45     ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-01-19  3:28     ` Wei Zhao
2018-01-21 21:22       ` Mcnamara, John
2018-01-22  5:27         ` Zhao1, Wei
2018-01-22  5:18       ` [dpdk-dev] [PATCH v5] " Wei Zhao
2018-01-23 10:22         ` Mcnamara, John
2018-01-23 15:01           ` Zhang, Helin

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=A2573D2ACFCADC41BB3BE09C6DE313CA07C99E7B@PGSMSX103.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=helin.zhang@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=thomas@monjalon.net \
    /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).