From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] docs: add statistics read frequency to fm10k guide
Date: Tue, 9 Feb 2016 15:00:51 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20244FFBE@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <11831068.7FU8aLYTU0@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, February 8, 2016 4:01 PM
> To: Van Haaren, Harry <harry.van.haaren@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] docs: add statistics read frequency to
> fm10k guide
>
> 2016-02-08 15:42, Harry van Haaren:
> > This patch documents that the statistics of fm10k based NICs must be
> > read regularly in order to avoid an undetected 32 bit integer-overflow.
> >
> > Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> > ---
> > doc/guides/nics/fm10k.rst | 16 ++++++++++++++++
> > doc/guides/rel_notes/release_2_3.rst | 4 ++++
>
> Thanks for improving the doc.
> I think we should not add it to the release notes. Other opinions?
In general it shouldn't be required to add a note about doc changes to the release note.
In this case the note part may make more sense in the "Known Issues" section of the release note.
John.
--
next prev parent reply other threads:[~2016-02-09 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 15:42 Harry van Haaren
2016-02-08 16:00 ` Thomas Monjalon
2016-02-08 16:06 ` Van Haaren, Harry
2016-02-09 15:00 ` Mcnamara, John [this message]
2016-02-09 15:19 ` [dpdk-dev] [PATCH v2] " Harry van Haaren
2016-02-22 17:13 ` Mcnamara, John
2016-02-22 17:18 ` Mcnamara, John
2016-02-22 17:40 ` Thomas Monjalon
2016-03-06 22:35 ` Thomas Monjalon
2016-03-08 17:16 ` [dpdk-dev] [PATCH v3] " Harry van Haaren
2016-03-09 17:39 ` Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE20244FFBE@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=thomas.monjalon@6wind.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).