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 74FE843A9F; Wed, 7 Feb 2024 14:31:19 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1864C40295; Wed, 7 Feb 2024 14:31:19 +0100 (CET) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by mails.dpdk.org (Postfix) with ESMTP id 0B97840279 for ; Wed, 7 Feb 2024 14:31:17 +0100 (CET) Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailout.west.internal (Postfix) with ESMTP id E68DE3200392; Wed, 7 Feb 2024 08:31:14 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 07 Feb 2024 08:31:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1707312674; x=1707399074; bh=rlfANRk9j2Dnh+U7dVqBbcv7Op8Nzl21NjhKroMV8fU=; b= b/M4QGnpbLv8Shc8YqX5ThN/JalSIQeE6/mG/Nwq+gwgMI8unowgXdOaiHLGlnio qpqVMP7vp1tkKic9ZvnBYI0+ccnD4f/Ofq49ZRvAkhtg41NAeP5UY+T5mkkS5xtf UcH64F7osT/lSfrXRRyU6xgd2+Qilp5v1THzM/OKAnFzuCkJbcpHZRBJ6NXp4Ob2 EBk+AJfMDOJSXfK6zyROFuDQ3airqCIiQoOraMD3NmB/SJ9IS9Qpan0gZwJpetka KEkXx+2nuiD6OiWnVP7blaO0fb77ZMqAOdbYHH6MRBpUOLl6grli1Oyj2VQzP3Kb fnJWFAPC67tkz1M2I+siQQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1707312674; x= 1707399074; bh=rlfANRk9j2Dnh+U7dVqBbcv7Op8Nzl21NjhKroMV8fU=; b=W quli1Qz3zSwq1IDLGXr5zm5QsUGrlK7N3JCjB4oPATdmGmhVFwnQ5fjcDd2AJARc e92iNrOcSSUPlrePA1VMJ67ikaeoeWNYnU54yJB2U05MgKWHHKu+1Hv6YEEW/7QQ cLOedHXuhvmo4dZiyw4R9KjNqgjUXE2tYvh3xqoX3ybaV21orDpghDouROBBZipM 0xfT3LSFIql6VDSDKafZS7XP/UnSj+8uhwOCO1znf5I04JoNLnpanKJOjufy3JhF 9zNcD2KDmjM5cCRrJvxIqJP4B8bnRtpktZL4dIUth+08B1x7Ej1CKs6ZS7lvFXDs A9O0gjuPDWYb3E7Aq3dRw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrtddvgdehtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 7 Feb 2024 08:31:12 -0500 (EST) From: Thomas Monjalon To: Dariusz Sosnowski , "Mcnamara, John" , Ferruh Yigit Cc: Matan Azrad , Viacheslav Ovsiienko , Ori Kam , Suanming Mou , Andrew Rybchenko , dev@dpdk.org Subject: Re: [PATCH v3] ethdev: fast path async flow API Date: Wed, 07 Feb 2024 14:31:11 +0100 Message-ID: <1923081.6tgchFWduM@thomas> In-Reply-To: <00761c83-1843-420d-aaeb-d9e49329e191@amd.com> References: <20240131093523.1553028-1-dsosnowski@nvidia.com> <00761c83-1843-420d-aaeb-d9e49329e191@amd.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 07/02/2024 11:56, Ferruh Yigit: > As we synced with Dariusz, there is no good place to document > ethdev-drivers interfaces in the release notes. > > Also this release there were more ethdev-drivers interface changes, > around get_ptype(), but those also not documented in the release notes, > so will remove these ones too. > > > But for further release notes, @Thomas, @John, what do you think to add > a new section (or sub-section) for "internal interface" ?? (device > abstraction - drivers) interface changes? When a driver interface is changed, the drivers are updated accordingly. If it's a driver addition, then we need to follow-up with drivers maintainers. Adding a new section in the release notes for driver interface changes is possible but means more work. I'm afraid a lot of changes won't be described, so I'm not sure of the value of such incomplete doc.