From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 82F09A00C2; Wed, 17 Mar 2021 07:57:09 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0114F242B12; Wed, 17 Mar 2021 07:57:09 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 9E9CC4014D for ; Wed, 17 Mar 2021 07:57:07 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 339F05C010E; Wed, 17 Mar 2021 02:57:05 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 17 Mar 2021 02:57:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm3; bh= Yi/jcePyFnhtI6TAkE9SW5ZL7FqaBGzwMNra3ZnIPZw=; b=w5yvrToRWNcfiBXU LtjG5tg9KJklZktcpIR3gza6UclChS7v23xTX/qNnPOcSK7qXCju6BBxGPY3NP6n KWzrFPOUMnyoIBJYJAvZyl5uZEcWX4UrY54nbboww1Bc+D11ZLOAri7ESeI4eFgV uOL1Wo161RKqFJPADHF3e60npLdwMhhh3e5z8LMYxpK+KY+4ewL6IpszwzRuSoFI exK/HMa3O/xvYZqjDr2AhEMihAAdjit0rbjQJuNnbcHc70FFIIPnyevDTOID+CmW LTVoOL0yyTPhgARKZu0A8mYFdVhkmZAMMZt2HVh0qVSsji6gcNtuLnIXJZdTI3AT sANeJA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Yi/jcePyFnhtI6TAkE9SW5ZL7FqaBGzwMNra3ZnIP Zw=; b=LCyOOVIJoKNINDLhrYbaKjeTV5vglpkbm/oJVPoA5c3K/mUGbmHpr/D4Z BAQ3JYNa+1k6jO4CHCapmxH9lWfOfq5mclRmbKzvMnmTUuRk5ObsEDjGh49wfH3w g6c8KS++DBh7J0q0o9xv/DB/lIjj7tNa6FNROzIcQMcSmOWqC2P4IkhprJP1cHQR zDpxQ1kB0fDcXzLlJpmgJ3AO8FEphuvIwwTH2cGxiEQnnAPB3o16HDUyWiy1ZJMY sBqTofSUjduPZjfzJAK/UYi/mL6i68fu2lI8h6lw2TJtdhf2iuCDfud5cvjLMfvC xPMtTmZA5QxqPYFwW4Yu5JVpqNT1g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeffedgleelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id F2F4E1080064; Wed, 17 Mar 2021 02:57:02 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: Xueming Li , Andrew Rybchenko , dev@dpdk.org, Viacheslav Ovsiienko , Asaf Penso , mdr@ashroe.eu, bruce.richardson@intel.com, david.marchand@redhat.com Date: Wed, 17 Mar 2021 07:57:00 +0100 Message-ID: <3346773.ZxYClqdKVh@thomas> In-Reply-To: <261eaa95-ba44-9085-94ac-97c78e4afb94@intel.com> References: <1608303356-13089-2-git-send-email-xuemingl@nvidia.com> <1670440.A2tmBZZM1K@thomas> <261eaa95-ba44-9085-94ac-97c78e4afb94@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 17/03/2021 00:34, Ferruh Yigit: > 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? In general, a new API comes with a new feature description. The API changes section is for documenting what must be adapted in the applications. If we add more info in this section, I'm afraid it will be less straightforward for those who just need to maintain apps.