From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>, zhoumin@loongson.cn
Subject: |WARNING| pw137518-137520 [PATCH v4 1/3] common/qat: isolate parser arguments configuration
Date: Fri, 1 Mar 2024 03:04:30 +0800 [thread overview]
Message-ID: <202402291904.41TJ4UlK2700822@localhost.localdomain> (raw)
In-Reply-To: <20240229191427.1267-1-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/137518
_apply patch failure_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thu, 29 Feb 2024 19:14:25 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 8f27705b70911d12dc0f356a728d73279fbc1e84
Apply patch set 137518-137520 failed:
Checking patch drivers/common/qat/qat_common.c...
Checking patch drivers/common/qat/qat_common.h...
Checking patch drivers/common/qat/qat_device.c...
Hunk #1 succeeded at 124 (offset 3 lines).
error: while searching for:
}
}
struct qat_pci_device *
qat_pci_device_allocate(struct rte_pci_device *pci_dev,
struct qat_dev_cmd_param *qat_dev_cmd_param)
{
struct qat_pci_device *qat_dev;
enum qat_device_gen qat_dev_gen;
error: patch failed: drivers/common/qat/qat_device.c:210
error: drivers/common/qat/qat_device.c: patch does not apply
Checking patch drivers/common/qat/qat_device.h...
error: while searching for:
/**< Per generation specific information */
uint32_t slice_map;
/**< Map of the crypto and compression slices */
};
struct qat_gen_hw_data {
error: patch failed: drivers/common/qat/qat_device.h:135
error: drivers/common/qat/qat_device.h: patch does not apply
Checking patch drivers/compress/qat/qat_comp_pmd.c...
error: while searching for:
&qat_comp_gen_dev_ops[qat_pci_dev->qat_dev_gen];
uint64_t capa_size;
uint16_t sub_id = qat_dev_instance->pci_dev->id.subsystem_device_id;
snprintf(name, RTE_COMPRESSDEV_NAME_MAX_LEN, "%s_%s",
qat_pci_dev->name, "comp");
error: patch failed: drivers/compress/qat/qat_comp_pmd.c:683
error: drivers/compress/qat/qat_comp_pmd.c: patch does not apply
Checking patch drivers/compress/qat/qat_comp_pmd.h...
Checking patch drivers/crypto/qat/qat_asym.c...
error: while searching for:
&qat_asym_gen_dev_ops[qat_pci_dev->qat_dev_gen];
char name[RTE_CRYPTODEV_NAME_MAX_LEN];
char capa_memz_name[RTE_CRYPTODEV_NAME_MAX_LEN];
int i = 0;
uint16_t slice_map = 0;
uint16_t sub_id = qat_dev_instance->pci_dev->id.subsystem_device_id;
snprintf(name, RTE_CRYPTODEV_NAME_MAX_LEN, "%s_%s",
qat_pci_dev->name, "asym");
error: patch failed: drivers/crypto/qat/qat_asym.c:1515
error: drivers/crypto/qat/qat_asym.c: patch does not apply
Checking patch drivers/crypto/qat/qat_sym.c...
error: while searching for:
const struct qat_crypto_gen_dev_ops *gen_dev_ops =
&qat_sym_gen_dev_ops[qat_pci_dev->qat_dev_gen];
uint16_t sub_id = qat_dev_instance->pci_dev->id.subsystem_device_id;
snprintf(name, RTE_CRYPTODEV_NAME_MAX_LEN, "%s_%s",
qat_pci_dev->name, "sym");
error: patch failed: drivers/crypto/qat/qat_sym.c:203
error: drivers/crypto/qat/qat_sym.c: patch does not apply
next parent reply other threads:[~2024-02-29 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229191427.1267-1-arkadiuszx.kusztal@intel.com>
2024-02-29 19:04 ` qemudev [this message]
2024-02-29 19:16 ` |WARNING| pw137518 " 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=202402291904.41TJ4UlK2700822@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).