DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Srujana Challa <schalla@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Subject: RE: [EXTERNAL] Re: [PATCH v1] Revert "doc: extension of crypto event callback announced"
Date: Wed, 9 Oct 2024 19:46:22 +0000	[thread overview]
Message-ID: <CO6PR18MB44845F25C11C9340C0380A9AD87F2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20241007103143.00a66e97@hermes.local>

> On Thu, 1 Aug 2024 13:06:07 +0530
> Srujana Challa <schalla@marvell.com> wrote:
> 
> > The previously planned update to the `rte_cryptodev_cb_fn` function
> > prototype is being reverted. The introduction of the
> > `rte_cryptodev_queue_pair_event_error_query` API provides a means for
> > applications to retrieve the queue pair ID that encountered an error
> > interrupt. This makes the addition of the `qp_id` parameter to the
> > `rte_cryptodev_cb_fn` function unnecessary, and as such, the proposed
> > extension is no longer required.
> >
> > Signed-off-by: Srujana Challa <schalla@marvell.com>
> 
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Akhil Goyal <gakhil@marvell.com>

Applied to dpdk-next-crypto
Thanks.

      reply	other threads:[~2024-10-09 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01  7:11 [PATCH] " Srujana Challa
2024-08-01  7:36 ` [PATCH v1] " Srujana Challa
2024-10-07 17:31   ` Stephen Hemminger
2024-10-09 19:46     ` Akhil Goyal [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=CO6PR18MB44845F25C11C9340C0380A9AD87F2@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=schalla@marvell.com \
    --cc=stephen@networkplumber.org \
    /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).