From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Wenbo Cao <caowenbo@mucse.com>, zhoumin@loongson.cn
Subject: |WARNING| pw129788 [[PATCH v1] 5/8] net/rnp add reset code for Chip Init process
Date: Tue, 1 Aug 2023 18:24:25 +0800 [thread overview]
Message-ID: <202308011024.371AOPcG1096249@localhost.localdomain> (raw)
In-Reply-To: <20230801064346.805294-6-caowenbo@mucse.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/129788
_apply patch failure_
Submitter: Wenbo Cao <caowenbo@mucse.com>
Date: Tue, 1 Aug 2023 06:43:43 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 0ae35eceb9e4569b0814fcf671b4455301bb7518
Apply patch set 129788 failed:
Checking patch drivers/net/rnp/base/rnp_api.c...
/home/zhoumin/dpdk-ci/tools/../series/29074/129788.patch:114: new blank line at EOF.
+
Checking patch drivers/net/rnp/base/rnp_api.h...
Checking patch drivers/net/rnp/base/rnp_cfg.h...
Checking patch drivers/net/rnp/base/rnp_dma_regs.h...
Checking patch drivers/net/rnp/base/rnp_eth_regs.h...
Checking patch drivers/net/rnp/base/rnp_hw.h...
error: drivers/net/rnp/base/rnp_hw.h: No such file or directory
Checking patch drivers/net/rnp/meson.build...
error: drivers/net/rnp/meson.build: No such file or directory
Checking patch drivers/net/rnp/rnp.h...
error: drivers/net/rnp/rnp.h: No such file or directory
Checking patch drivers/net/rnp/rnp_ethdev.c...
error: drivers/net/rnp/rnp_ethdev.c: No such file or directory
Checking patch drivers/net/rnp/rnp_mbx_fw.c...
Checking patch drivers/net/rnp/rnp_mbx_fw.h...
error: drivers/net/rnp/rnp_mbx_fw.h: No such file or directory
next parent reply other threads:[~2023-08-01 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230801064346.805294-6-caowenbo@mucse.com>
2023-08-01 10:24 ` qemudev [this message]
2023-08-01 10:34 ` 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=202308011024.371AOPcG1096249@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=caowenbo@mucse.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).