From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Vladimir Medvedkin <vladimir.medvedkin@intel.com>, zhoumin@loongson.cn
Subject: |WARNING| pw150645 [PATCH] net/ice: fix how ice driver handles flows
Date: Thu, 30 Jan 2025 23:16:19 +0800 [thread overview]
Message-ID: <202501301516.50UFGJ9P3177583@localhost.localdomain> (raw)
In-Reply-To: <20250130155011.2658800-1-vladimir.medvedkin@intel.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/150645
_apply patch failure_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Thu, 30 Jan 2025 15:50:11 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 9ab5a5f30c4be9f12ddaf50aec3435986bc5a495
Apply patch set 150645 failed:
Checking patch drivers/net/ice/ice_generic_flow.c...
error: drivers/net/ice/ice_generic_flow.c: No such file or directory
next parent reply other threads:[~2025-01-30 15:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250130155011.2658800-1-vladimir.medvedkin@intel.com>
2025-01-30 15:16 ` qemudev [this message]
2025-01-30 15:49 ` |SUCCESS| " checkpatch
2025-01-30 16:43 ` 0-day Robot
2025-01-30 17:35 ` dpdklab
2025-01-30 17:48 ` dpdklab
2025-01-30 17:54 ` dpdklab
2025-01-30 17:56 ` |PENDING| " dpdklab
2025-01-30 17:57 ` dpdklab
2025-01-30 18:01 ` |SUCCESS| " dpdklab
2025-01-30 18:02 ` dpdklab
2025-01-30 19:28 ` |PENDING| " dpdklab
2025-01-30 19:33 ` |SUCCESS| " dpdklab
2025-01-30 20:46 ` dpdklab
2025-01-30 21:28 ` dpdklab
2025-01-30 22:23 ` |WARNING| " dpdklab
2025-01-30 22:30 ` |PENDING| " dpdklab
2025-01-30 22:43 ` |WARNING| " dpdklab
2025-01-31 0:26 ` |SUCCESS| " dpdklab
2025-01-31 5:19 ` dpdklab
2025-01-31 5:19 ` dpdklab
2025-01-31 5:25 ` dpdklab
2025-02-04 20:55 ` dpdklab
2025-02-05 4:09 ` |WARNING| " dpdklab
2025-02-05 17:11 ` |SUCCESS| " dpdklab
2025-02-06 11:01 ` 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=202501301516.50UFGJ9P3177583@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
--cc=vladimir.medvedkin@intel.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).