From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH v2] docs: add statistics read frequency to
	fm10k guide
Date: Mon, 22 Feb 2016 18:40:41 +0100
Message-ID: <1700761.WB86EvbuoI@xps13>
References: <1454946137-5505-1-git-send-email-harry.van.haaren@intel.com>
 <1455031194-27921-1-git-send-email-harry.van.haaren@intel.com>
 <B27915DBBA3421428155699D51E4CFE20245E3E6@IRSMSX103.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: "Mcnamara, John" <john.mcnamara@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50])
 by dpdk.org (Postfix) with ESMTP id 61E142C36
 for <dev@dpdk.org>; Mon, 22 Feb 2016 18:42:16 +0100 (CET)
Received: by mail-wm0-f50.google.com with SMTP id c200so183520732wme.0
 for <dev@dpdk.org>; Mon, 22 Feb 2016 09:42:16 -0800 (PST)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20245E3E6@IRSMSX103.ger.corp.intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2016-02-22 17:18, Mcnamara, John:
> >  Known Issues
> >  ------------
> > 
> > +* **FM10K: Statistics Polling Frequency**
> > +
> > +  A section has been added to the NIC guide for fm10k about the maximum
> > + time between reading statistics and 32 bit packet counter overflows.
> 
> Hi Thomas,
> 
> We should probably call this section "New Known Issues" and then copy them to the legacy "Known Issues" doc after 1 release.
> 
>     http://dpdk.org/doc/guides/rel_notes/release_2_2.html#known-issues
>     http://dpdk.org/doc/guides/rel_notes/known_issues.html
> 
> Or any other suggestion?

Yes it is an option.
Or we can simply maintain known issues in one place and remove the
per-release section.