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 35A9946BD9; Mon, 21 Jul 2025 19:49:45 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C7EAD4026C; Mon, 21 Jul 2025 19:49:44 +0200 (CEST) Received: from fout-a5-smtp.messagingengine.com (fout-a5-smtp.messagingengine.com [103.168.172.148]) by mails.dpdk.org (Postfix) with ESMTP id 232344021E for ; Mon, 21 Jul 2025 19:49:44 +0200 (CEST) Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfout.phl.internal (Postfix) with ESMTP id C0530EC0288; Mon, 21 Jul 2025 13:49:43 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-09.internal (MEProxy); Mon, 21 Jul 2025 13:49:43 -0400 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=fm2; t=1753120183; x=1753206583; bh=XRHA1MeUZ8w+1Hz1W4Qt5jfAtK7iKrxgstE/fJbb4as=; b= SbBiq/SmTiBibp/LxAVzF4uX8JFsI5ChM/2cjYI5UbhWPTNOJzcUXkDb3wWr6QjX T1MvBIrnXd9oJNqjTmBAHu3wVgQe+weWuj5obI5olg5O6lC1gpTzc6hdAX7RffuN JE+5cmkkHEdfaTBvZXhGx04DqoFWlK5s9YX7Ps9HsJgTAKhzx79iphH3ax04zoNw ElEf25PU0RL4gQi1qCjEICTihAPDFEERRjrTmVTz4p7YIha7O/Ph1X8cZryb5ZZV kMQrDk5iU3KbKfozJihQAuYw5QlqRSw4BV/QQ4ZaoYSnBSRKWe1SqbVjGhCUsQUr zR+TkMRaQvXa66UrtnttOg== 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-sender:x-me-sender:x-sasl-enc; s=fm2; t=1753120183; x= 1753206583; bh=XRHA1MeUZ8w+1Hz1W4Qt5jfAtK7iKrxgstE/fJbb4as=; b=V FxNa+mpCkynW3KbHoqOiFc5xbXV3xT7mJ7WpEhrnyBbvhnS7gQPeGC7+pwU78iOb RrKq2GcIssIwShWnuZv8y+5c+k5DjyjI5V21xwgou6FTzQop9nO1NFO3jpCwkkvy 94+9+zVKyHnynDawfC67R7icTi7TnxalU8w7VJz+CP+NyKv5JzDBux0ERsfYp/nV d5wWs8YkTOp32apVK+rDAibUlIIL4bAdLZ6K1DjCALnZ6lUn1lc9enibPSq4g2CO oF2rFQ25InR+i0KSa8+bIaGBRoQu+MsRDVlf+qFhhSCuiSoKc81ZsomqmGCPAa7J peXjPoWTQUzKA3qzYgYlg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdejvdejvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefhvfevufffkfgjfhgggfgtsehtufertddttdejnecuhfhrohhmpefvhhhomhgrshcu ofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuggftrf grthhtvghrnhepjeduveehieevuddutdevfffgtdegkeeuveejffejgedtgeegkefgvdeu gfefkeejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthdpnhgspghrtghpthhtohepudehpdhm ohguvgepshhmthhpohhuthdprhgtphhtthhopehpsghhrghgrghvrghtuhhlrgesmhgrrh hvvghllhdrtghomhdprhgtphhtthhopegrmhhithhprhgrkhgrshhhshesmhgrrhhvvghl lhdrtghomhdprhgtphhtthhopehjvghrihhnjhesmhgrrhhvvghllhdrtghomhdprhgtph htthhopeguvghvseguphgukhdrohhrghdprhgtphhtthhopehvrghtthhunhhurhhusehm rghrvhgvlhhlrdgtohhmpdhrtghpthhtohepghdrshhinhhghhesnhigphdrtghomhdprh gtphhtthhopehsrggthhhinhdrshgrgigvnhgrsehngihprdgtohhmpdhrtghpthhtohep hhgvmhgrnhhtrdgrghhrrgifrghlsehngihprdgtohhmpdhrtghpthhtohepfhgvnhhgtg hhvghnghifvghnsehhuhgrfigvihdrtghomh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 21 Jul 2025 13:49:40 -0400 (EDT) From: Thomas Monjalon To: Pavan Nikhilesh Bhagavatula , Amit Prakash Shukla Cc: Jerin Jacob , dev@dpdk.org, Vamsi Krishna Attunuru , "g.singh@nxp.com" , "sachin.saxena@nxp.com" , "hemant.agrawal@nxp.com" , "fengchengwen@huawei.com" , "bruce.richardson@intel.com" , "kevin.laatz@intel.com" , "conor.walsh@intel.com" , Gowrishankar Muthukrishnan , Vidya Sagar Velumuri , "anatoly.burakov@intel.com" Subject: Re: [EXTERNAL] [PATCH] doc: announce DMA configuration structure changes Date: Mon, 21 Jul 2025 19:49:39 +0200 Message-ID: <3307880.vfdyTQepKt@thomas> In-Reply-To: References: <20250416110541.10358-1-pbhagavatula@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 > Deprecate rte_dma_conf structure to allow for a more flexible > configuration of DMA devices. > The new structure will have a flags field instead of multiple > boolean fields for each feature. > > Signed-off-by: Pavan Nikhilesh > --- > +* dmadev: The ``rte_dma_conf`` structure is updated to include a new field > + ``rte_dma_conf::flags`` that should be used to configure dmadev features. > + The existing field ``rte_dma_conf::enable_silent`` is removed and replaced > + with the new flag ``RTE_DMA_CFG_FLAG_SILENT``, to configure silent mode > + the flag should be set in ``rte_dma_conf::flags`` during device configuration. > > Acked-by: Amit Prakash Shukla There is only 1 ack. Per our policy, it will miss the release 25.07. You can probably do this change anyway, and keep ABI compatibility by versioning the function.