From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5] doc: add queue region feature info to release notes
Date: Tue, 23 Jan 2018 15:01:39 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71AD1D4FA@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23EE7F396@IRSMSX103.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mcnamara, John
> Sent: Tuesday, January 23, 2018 6:22 PM
> To: Zhao1, Wei; dev@dpdk.org
> Cc: thomas@monjalon.net; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v5] doc: add queue region feature info to
> release notes
>
>
>
> > -----Original Message-----
> > From: Zhao1, Wei
> > Sent: Monday, January 22, 2018 5:19 AM
> > To: dev@dpdk.org
> > Cc: Mcnamara, John <john.mcnamara@intel.com>; thomas@monjalon.net;
> > stable@dpdk.org; Zhao1, Wei <wei.zhao1@intel.com>
> > Subject: [PATCH v5] 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.
> >
> > ...
> > +Queue region configuration
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The underline for a section header should match the length of the text and
> should be followed by a blank line, line in my suggested changes.
>
> See also:
> http://dpdk.org/doc/guides/contributing/documentation.html#section-
> headers
>
> However, this isn't an error so:
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied to dpdk-next-net-intel, with commit log changes. Thanks!
/Helin
>
>
prev parent reply other threads:[~2018-01-23 15:01 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
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 [this message]
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=F35DEAC7BCE34641BA9FAC6BCA4A12E71AD1D4FA@SHSMSX103.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=wei.zhao1@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).