automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>, zhoumin@loongson.cn
Subject: |WARNING| pw137679-137681 [PATCH v5 1/3] common/qat: isolate parser arguments configuration
Date: Sat, 2 Mar 2024 10:58:37 +0800	[thread overview]
Message-ID: <202403020258.4222wbxP3520424@localhost.localdomain> (raw)
In-Reply-To: <20240301155251.5101-1-arkadiuszx.kusztal@intel.com>

Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/137679

_apply patch failure_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Fri,  1 Mar 2024 15:52:49 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 5ac50824383c2683c0dfdf24c6dc493f1fa54852

Apply patch set 137679-137681 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 127 (offset -3 lines).
Hunk #2 succeeded at 162 (offset -5 lines).
Hunk #3 succeeded at 255 (offset -5 lines).
Hunk #4 succeeded at 335 (offset -6 lines).
Hunk #5 succeeded at 381 (offset -5 lines).
Hunk #6 succeeded at 453 (offset -5 lines).
Hunk #7 succeeded at 472 (offset -5 lines).
Hunk #8 succeeded at 480 (offset -5 lines).
Hunk #9 succeeded at 517 (offset -5 lines).
Hunk #10 succeeded at 541 (offset -5 lines).
Checking patch drivers/common/qat/qat_device.h...
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:210
error: drivers/crypto/qat/qat_sym.c: patch does not apply


      parent reply	other threads:[~2024-03-02  3:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301155251.5101-1-arkadiuszx.kusztal@intel.com>
2024-03-01 15:54 ` |SUCCESS| pw137679 " checkpatch
2024-03-02  2:58 ` qemudev [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=202403020258.4222wbxP3520424@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).