automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Junfeng Guo <junfeng.guo@intel.com>, zhoumin@loongson.cn
Subject: |WARNING| pw134884 [PATCH] raw/ntb: refactor to support NTB on 5th Gen Intel Xeon
Date: Wed, 6 Dec 2023 11:05:10 +0800	[thread overview]
Message-ID: <202312060305.3B635A171306519@localhost.localdomain> (raw)
In-Reply-To: <20231206030025.2334584-1-junfeng.guo@intel.com>

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

_apply patch failure_

Submitter: Junfeng Guo <junfeng.guo@intel.com>
Date: Wed,  6 Dec 2023 11:00:25 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a526461b0764de52b09b073df84f9e87ec120c93

Apply patch set 134884 failed:

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

* **Improved support of RSS hash algorithm.**

  * Added new function ``rte_eth_find_rss_algo`` to get RSS hash

error: patch failed: doc/guides/rel_notes/release_24_03.rst:55
error: doc/guides/rel_notes/release_24_03.rst: patch does not apply
Checking patch drivers/raw/ntb/ntb.c...
Checking patch drivers/raw/ntb/ntb.h...
Checking patch drivers/raw/ntb/ntb_hw_intel.c...
Checking patch drivers/raw/ntb/ntb_hw_intel.h...
Checking patch usertools/dpdk-devbind.py...


  parent reply	other threads:[~2023-12-06  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231206030025.2334584-1-junfeng.guo@intel.com>
2023-12-06  3:03 ` |SUCCESS| " checkpatch
2023-12-06  3:05 ` qemudev [this message]
2023-12-06  3:23 |WARNING| " dpdklab

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=202312060305.3B635A171306519@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=junfeng.guo@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).