DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Vamsi Attunuru" <vattunuru@marvell.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	dev@dpdk.org
Cc: fengchengwen@huawei.com, kevin.laatz@intel.com,
	bruce.richardson@intel.com, jerinj@marvell.com,
	anoobj@marvell.com, Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [PATCH] doc: announce dmadev new capability addition
Date: Wed, 31 Jul 2024 12:24:33 +0200	[thread overview]
Message-ID: <22665936.hxa6pUQ8Du@thomas> (raw)
In-Reply-To: <CALBAE1ORvP51OgM1Hgks39nHG-rqYYV3M5_gu=NfYE-4CAfCsg@mail.gmail.com>

29/07/2024 17:20, Jerin Jacob:
> On Mon, Jul 29, 2024 at 6:19 PM Vamsi Attunuru <vattunuru@marvell.com> wrote:
> >
> > Announce addition of new capability flag and fields in
> 
> The new capability flag won't break ABI. We can mention only fields
> update rte_dma_info and rte_dma_conf structures.
> 
> Another option is new set APIs for priority enablement.  The downside
> is more code. All, opinions?
> 
> > rte_dma_info and rte_dma_conf structures.

I'm fine with just updating these structs.

> > Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>

Acked-by: Thomas Monjalon <thomas@monjalon.net>

Any other opinions?



  parent reply	other threads:[~2024-07-31 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 12:49 Vamsi Attunuru
2024-07-29 15:20 ` Jerin Jacob
2024-07-29 17:17   ` Morten Brørup
2024-07-31 10:24   ` Thomas Monjalon [this message]
2024-07-30 12:10 ` [PATCH v2] doc: announce changes to dma device structures Amit Prakash Shukla
2024-07-30 12:53 ` [PATCH v3] " Amit Prakash Shukla
2024-07-30 14:46   ` [PATCH v4] " Amit Prakash Shukla
2024-07-30 17:27     ` Jerin Jacob
2024-07-31 11:01       ` Thomas Monjalon
2024-07-31 16:06         ` Thomas Monjalon

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=22665936.hxa6pUQ8Du@thomas \
    --to=thomas@monjalon.net \
    --cc=anoobj@marvell.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=kevin.laatz@intel.com \
    --cc=mb@smartsharesystems.com \
    --cc=vattunuru@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).