automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Rakesh Kudurumalla <rkudurumalla@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw123933-123935 [PATCH v9 1/3] ethdev: skip congestion management configuration
Date: Wed, 15 Feb 2023 14:12:49 +0800	[thread overview]
Message-ID: <202302150612.31F6Cnm0237428@localhost.localdomain> (raw)
In-Reply-To: <20230215062532.1169860-1-rkudurumalla@marvell.com>

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

_apply patch failure_

Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Wed, 15 Feb 2023 11:55:30 +0530
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: a2a8cb4251308ce5ccbe391576fe6483c3adbc4c

Apply patch set 123933-123935 failed:

Checking patch doc/guides/nics/features/default.ini...
Hunk #1 succeeded at 200 (offset 2 lines).
Checking patch doc/guides/prog_guide/rte_flow.rst...
Hunk #1 succeeded at 1832 (offset -8 lines).
Checking patch doc/guides/rel_notes/release_23_03.rst...
error: while searching for:
  Added lock annotations attributes so that clang can statically analyze lock
  correctness.

* **Updated AMD axgbe driver.**

  * Added multi-process support.

error: patch failed: doc/guides/rel_notes/release_23_03.rst:60
error: doc/guides/rel_notes/release_23_03.rst: patch does not apply
Checking patch lib/ethdev/rte_flow.h...
Hunk #1 succeeded at 2820 (offset 84 lines).


       reply	other threads:[~2023-02-15  6:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230215062532.1169860-1-rkudurumalla@marvell.com>
2023-02-15  6:12 ` qemudev [this message]
2023-02-15  6:27 ` |SUCCESS| pw123933 " 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=202302150612.31F6Cnm0237428@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=rkudurumalla@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).