From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCHv3 1/5] ethdev: add new API to retrieve
	RX/TX	queue information
Date: Wed, 22 Jul 2015 22:45:02 +0200
Message-ID: <4626665.SuMZmzWyqM@xps13>
References: <1437394750-5965-1-git-send-email-konstantin.ananyev@intel.com>
 <F35DEAC7BCE34641BA9FAC6BCA4A12E70A8986AE@SHSMSX104.ccr.corp.intel.com>
 <2601191342CEEE43887BDE71AB97725836A28EB1@irsmsx105.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com
 [209.85.212.176]) by dpdk.org (Postfix) with ESMTP id 62D795A0C
 for <dev@dpdk.org>; Wed, 22 Jul 2015 22:46:16 +0200 (CEST)
Received: by wicmv11 with SMTP id mv11so97075425wic.0
 for <dev@dpdk.org>; Wed, 22 Jul 2015 13:46:16 -0700 (PDT)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836A28EB1@irsmsx105.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>

2015-07-22 17:00, Ananyev, Konstantin:
> From: Zhang, Helin
> > > -#ifdef __cplusplus
> > > -}
> > > -#endif
> > > -
> > >  /**
> > >   * Set the list of multicast addresses to filter on an Ethernet device.
> > >   *
> > > @@ -3882,4 +3952,9 @@ extern int
> > > rte_eth_timesync_read_rx_timestamp(uint8_t port_id,
> > >   */
> > >  extern int rte_eth_timesync_read_tx_timestamp(uint8_t port_id,
> > >  					      struct timespec *timestamp);
> > > +
> > > +#ifdef __cplusplus
> > > +}
> > > +#endif
> > This is fix for the issue introduced by new ieee1588. It must be added in R2.1 no matter
> > these patches can be applied or not.

Yes you're totally right Helin.
It's a fix and should be in a separate patch.
This feature is not planned in 2.1.