From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Srujana Challa <schalla@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw142804 [PATCH] Revert "doc: extension of crypto event callback announced"
Date: Thu, 1 Aug 2024 14:43:39 +0800 [thread overview]
Message-ID: <202408010643.4716hddl007984@localhost.localdomain> (raw)
In-Reply-To: <20240801071147.3020911-1-schalla@marvell.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/142804
_apply patch failure_
Submitter: Srujana Challa <schalla@marvell.com>
Date: Thu, 1 Aug 2024 12:41:47 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: b3485f4293997d35b6daecc3437bb0c183a51fb3
Apply patch set 142804 failed:
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
The legacy actions should be removed
once ``MODIFY_FIELD`` alternative is implemented in drivers.
* cryptodev: The function ``rte_cryptodev_cb_fn`` will be updated
to have another parameter ``qp_id`` to return the queue pair ID
which got error interrupt to the application,
so that application can reset that particular queue pair.
* cryptodev: The Intel IPsec Multi-Buffer version will be bumped
to a minimum version of v1.4.
This will effect the KASUMI, SNOW3G, ZUC, AESNI GCM, AESNI MB and CHACHAPOLY
error: patch failed: doc/guides/rel_notes/deprecation.rst:115
error: doc/guides/rel_notes/deprecation.rst: patch does not apply
next parent reply other threads:[~2024-08-01 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240801071147.3020911-1-schalla@marvell.com>
2024-08-01 6:43 ` qemudev [this message]
2024-08-01 7:13 ` |SUCCESS| " checkpatch
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=202408010643.4716hddl007984@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=schalla@marvell.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).