From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add queue region feature info to release notes
Date: Fri, 22 Dec 2017 03:52:46 +0000 [thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07C926A2@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <15ab0b70-164d-c8d0-283b-f46eb736d9f8@intel.com>
Ok, I will commit a new patch as this way.
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Friday, December 22, 2017 11:26 AM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Cc: Mcnamara, John <john.mcnamara@intel.com>; Zhang, Helin
> <helin.zhang@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] doc: add queue region feature info to
> release notes
>
> On 12/21/2017 5:36 PM, Zhao1, Wei wrote:
> > Ok, this will be updating in release notes for v18.02, and have a
> > mention that this feature has been implemented in v17.11?
>
> I think mentioning from first implemented release helps to reduce confusion,
> in case users interested in implementation details etc... But no strong opinion.
>
> >
> >
> >
> >> -----Original Message-----
> >> From: Yigit, Ferruh
> >> Sent: Friday, December 22, 2017 2:10 AM
> >> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> >> Cc: Mcnamara, John <john.mcnamara@intel.com>
> >> Subject: Re: [dpdk-dev] [PATCH] doc: add queue region feature info to
> >> release notes
> >>
> >> On 12/20/2017 7:52 PM, Wei Zhao wrote:
> >>> This patch add inforation about i40e queue region realted to release
> >>> notes, it has been missed before.
> >>>
> >>> Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> >>> ---
> >>> doc/guides/rel_notes/release_17_11.rst | 17 +++++++++++++++++
> >>
> >> I think we shouldn't update release notes once it has been released.
> >>
> >> Perhaps it can be an option to mention from this in latest release
> >> notes with a note that says actual support added in v17.11?
next prev parent reply other threads:[~2017-12-22 3:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 3:52 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 [this message]
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
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=A2573D2ACFCADC41BB3BE09C6DE313CA07C926A2@PGSMSX103.gar.corp.intel.com \
--to=wei.zhao1@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@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).