From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 75031A054F;
	Wed, 17 Mar 2021 00:34:55 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 1469240689;
	Wed, 17 Mar 2021 00:34:55 +0100 (CET)
Received: from mga05.intel.com (mga05.intel.com [192.55.52.43])
 by mails.dpdk.org (Postfix) with ESMTP id A0A4040040
 for <dev@dpdk.org>; Wed, 17 Mar 2021 00:34:53 +0100 (CET)
IronPort-SDR: TJdmwmawjzCow00oNYeeI065DJVZysYMD34zbm27CMIevRbSV4cmcMGyxzDXCNbDK6Xb7WG0gs
 bw3Qf1/MRcIA==
X-IronPort-AV: E=McAfee;i="6000,8403,9925"; a="274396502"
X-IronPort-AV: E=Sophos;i="5.81,254,1610438400"; d="scan'208";a="274396502"
Received: from orsmga001.jf.intel.com ([10.7.209.18])
 by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
 16 Mar 2021 16:34:52 -0700
IronPort-SDR: HVx0+T8mEDf+/Obr5olLb0yAgrETHxUtTuIOxmMrcClDXRjfVqObo8Srz1H+FAXTQNXDO2H6yw
 bWiS7CoRP7yQ==
X-IronPort-AV: E=Sophos;i="5.81,254,1610438400"; d="scan'208";a="449887530"
Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.252.24.201])
 ([10.252.24.201])
 by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
 16 Mar 2021 16:34:50 -0700
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Xueming Li <xuemingl@nvidia.com>,
 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>, dev@dpdk.org,
 Viacheslav Ovsiienko <viacheslavo@nvidia.com>, Asaf Penso
 <asafp@nvidia.com>, mdr@ashroe.eu
References: <1608303356-13089-2-git-send-email-xuemingl@nvidia.com>
 <1615468416-10115-9-git-send-email-xuemingl@nvidia.com>
 <24792649-623e-8326-5fe2-eab2c408f0f7@intel.com> <1670440.A2tmBZZM1K@thomas>
From: Ferruh Yigit <ferruh.yigit@intel.com>
X-User: ferruhy
Message-ID: <261eaa95-ba44-9085-94ac-97c78e4afb94@intel.com>
Date: Tue, 16 Mar 2021 23:34:42 +0000
MIME-Version: 1.0
In-Reply-To: <1670440.A2tmBZZM1K@thomas>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [dpdk-dev] [PATCH v9 08/10] ethdev: new API to get representor
 info
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 3/16/2021 9:19 PM, Thomas Monjalon wrote:
> 16/03/2021 20:18, Ferruh Yigit:
>> On 3/11/2021 1:13 PM, Xueming Li wrote:
>>> +	# added in 21.05
>>> +	rte_eth_representor_info_get;
>>
>> New API documented in release notes, "API Changes" section, while merging.
> 
> In general we don't mention new API in release notes.
> What is the intent Ferruh?
> 

Intent is just document new APIs.
I recognized that new APIs are not mentioned previously, is there a specific 
reason to it? Shouldn't be good to document them?