From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>, zhoumin@loongson.cn
Subject: |WARNING| pw136867 [PATCH v2] common/qat: add symmetric crypto virtual qat device (vQAT)
Date: Mon, 19 Feb 2024 06:03:06 +0800 [thread overview]
Message-ID: <202402182203.41IM36ot1873175@localhost.localdomain> (raw)
In-Reply-To: <20240218222557.13049-1-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/136867
_apply patch failure_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Sun, 18 Feb 2024 22:25:57 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 2b551097b3443ebf662e4d140600a4c9b108e73c
Apply patch set 136867 failed:
Checking patch doc/guides/rel_notes/release_24_03.rst...
error: while searching for:
Also, make sure to start the actual text at the margin.
=======================================================
Removed Items
-------------
error: patch failed: doc/guides/rel_notes/release_24_03.rst:55
error: doc/guides/rel_notes/release_24_03.rst: patch does not apply
Checking patch drivers/common/qat/dev/qat_dev_gen4.c...
Checking patch drivers/common/qat/qat_common.h...
Checking patch drivers/common/qat/qat_device.c...
Checking patch drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c...
Checking patch drivers/crypto/qat/qat_sym_session.c...
next parent reply other threads:[~2024-02-18 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240218222557.13049-1-arkadiuszx.kusztal@intel.com>
2024-02-18 22:03 ` qemudev [this message]
2024-02-18 22:26 ` |SUCCESS| pw136867 [PATCH v2] common/qat: add symmetric crypto virtual qat device vQAT checkpatch
2024-02-18 22:42 |WARNING| pw136867 [PATCH] [v2] common/qat: add symmetric crypto virtual qat device (vQAT) dpdklab
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=202402182203.41IM36ot1873175@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=arkadiuszx.kusztal@intel.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).