automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Viacheslav Ovsiienko <viacheslavo@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw123123-123131 [PATCH 1/9] ethdev: sharing indirect actions between ports
Date: Mon, 6 Feb 2023 17:42:04 +0800	[thread overview]
Message-ID: <202302060942.3169g4W22937586@localhost.localdomain> (raw)
In-Reply-To: <20230206095229.23027-1-viacheslavo@nvidia.com>

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

_apply patch failure_

Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Mon, 6 Feb 2023 11:52:21 +0200
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 74fce0da4e22931e6382d9345fb7e0ad360426f5

Apply patch set 123123-123131 failed:

Checking patch doc/guides/rel_notes/release_23_03.rst...
error: while searching for:
     Also, make sure to start the actual text at the margin.
     =======================================================

* **Updated Intel QuickAssist Technology (QAT) crypto driver.**

  * Added support for SHA3 224/256/384/512 plain hash in QAT GEN 3.

error: patch failed: doc/guides/rel_notes/release_23_03.rst:55
error: doc/guides/rel_notes/release_23_03.rst: patch does not apply
Checking patch doc/guides/testpmd_app_ug/testpmd_funcs.rst...
Hunk #1 succeeded at 3076 (offset 29 lines).


       reply	other threads:[~2023-02-06  9:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230206095229.23027-1-viacheslavo@nvidia.com>
2023-02-06  9:42 ` qemudev [this message]
2023-02-06  9:54 ` |WARNING| pw123123 " 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=202302060942.3169g4W22937586@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=test-report@dpdk.org \
    --cc=viacheslavo@nvidia.com \
    --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).