automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
	zhoumin@loongson.cn
Subject: |WARNING| pw132426-132432 [PATCH v4 1/7] crypto/openssl: include SM2 in asymmetric capabilities
Date: Mon, 9 Oct 2023 21:37:17 +0800	[thread overview]
Message-ID: <202310091337.399DbHNP1738607@localhost.localdomain> (raw)
In-Reply-To: <a5dad6cfc442aad38f0e77e8fa139b90094f5341.1696859505.git.gmuthukrishn@marvell.com>

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

_apply patch failure_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Mon, 9 Oct 2023 19:24:48 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 4dd146e597d81d900140a904e0b3b9feb1b0be6c

Apply patch set 132426-132432 failed:

Checking patch app/test/test_cryptodev_asym.c...
Checking patch app/test/test_cryptodev_sm2_test_vectors.h...
Checking patch doc/guides/rel_notes/release_23_11.rst...
error: while searching for:
* security: Removed deprecated field ``reserved_opts`` from struct
  ``rte_security_ipsec_sa_options``.


API Changes
-----------

error: patch failed: doc/guides/rel_notes/release_23_11.rst:122
error: doc/guides/rel_notes/release_23_11.rst: patch does not apply
Checking patch drivers/crypto/openssl/rte_openssl_pmd_ops.c...
Checking patch lib/cryptodev/rte_crypto_asym.h...
Hunk #1 succeeded at 69 (offset 5 lines).
Hunk #2 succeeded at 379 (offset 5 lines).
Hunk #3 succeeded at 635 (offset 5 lines).
Hunk #4 succeeded at 645 (offset 5 lines).


       reply	other threads:[~2023-10-09 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a5dad6cfc442aad38f0e77e8fa139b90094f5341.1696859505.git.gmuthukrishn@marvell.com>
2023-10-09 13:37 ` qemudev [this message]
2023-10-09 13:56 ` |SUCCESS| pw132426 " 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=202310091337.399DbHNP1738607@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=gmuthukrishn@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).