DPDK patches and discussions
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Amit Prakash Shukla <amitprakashs@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
	Vamsi Krishna Attunuru <vattunuru@marvell.com>,
	"g.singh@nxp.com" <g.singh@nxp.com>,
	"sachin.saxena@nxp.com" <sachin.saxena@nxp.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"kevin.laatz@intel.com" <kevin.laatz@intel.com>,
	"conor.walsh@intel.com" <conor.walsh@intel.com>,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
	Vidya Sagar Velumuri <vvelumuri@marvell.com>,
	"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>
Subject: Re: [EXTERNAL] [PATCH] doc: announce DMA configuration structure changes
Date: Sat, 26 Jul 2025 08:55:18 +0800	[thread overview]
Message-ID: <315e032d-c022-4ea2-b734-3d3a07f5ebc2@huawei.com> (raw)
In-Reply-To: <PH0PR18MB40865EFFF34A38C49079F979DE59A@PH0PR18MB4086.namprd18.prod.outlook.com>

Acked-by: Chengwen Feng <fengchengwen@huawei.com>

On 2025/7/25 14:04, Pavan Nikhilesh Bhagavatula wrote:
>>> 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 <mailto:pbhagavatula@marvell.com>
>>> ---
>>> +* 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 <amitprakashs@marvell.com>
>>
>> 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.
> 
> Hi Fengchengwen,
> 
> Are you ok with this change? If so please ack it so that I can work on getting
> an exception from techboard to merge this without deprecation notice in 25.11.
> 
> Thanks,
> Pavan.
> 


      reply	other threads:[~2025-07-26  0:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 11:05 pbhagavatula
2025-06-24  6:22 ` [EXTERNAL] " Amit Prakash Shukla
2025-07-21 17:49   ` Thomas Monjalon
2025-07-25  6:04     ` Pavan Nikhilesh Bhagavatula
2025-07-26  0:55       ` fengchengwen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=315e032d-c022-4ea2-b734-3d3a07f5ebc2@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=amitprakashs@marvell.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=conor.walsh@intel.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=gmuthukrishn@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=kevin.laatz@intel.com \
    --cc=pbhagavatula@marvell.com \
    --cc=sachin.saxena@nxp.com \
    --cc=thomas@monjalon.net \
    --cc=vattunuru@marvell.com \
    --cc=vvelumuri@marvell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).