From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw158397 [PATCH v3 44/44] net/netvsc: use LIST_FOREACH_SAFE
Date: Mon, 3 Nov 2025 13:57:51 -0500 [thread overview]
Message-ID: <20251103185751.539590-1-robot@bytheb.org> (raw)
In-Reply-To: <20251103164915.101713-45-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/158397/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/19044205313
next prev parent reply other threads:[~2025-11-03 18:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251103164915.101713-45-stephen@networkplumber.org>
2025-11-03 16:56 ` |WARNING| " checkpatch
2025-11-03 17:25 ` |FAILURE| pw158354-158397 [PATCH] [v3,44/44] net/netvsc: use LIST_FO dpdklab
2025-11-03 17:26 ` |SUCCESS| " dpdklab
2025-11-03 17:28 ` dpdklab
2025-11-03 17:33 ` |FAILURE| " dpdklab
2025-11-03 17:37 ` |PENDING| " dpdklab
2025-11-03 17:54 ` |SUCCESS| " dpdklab
2025-11-03 17:55 ` |PENDING| " dpdklab
2025-11-03 17:57 ` |FAILURE| " dpdklab
2025-11-03 17:59 ` |SUCCESS| " dpdklab
2025-11-03 18:04 ` dpdklab
2025-11-03 18:04 ` dpdklab
2025-11-03 18:05 ` |PENDING| " dpdklab
2025-11-03 18:15 ` dpdklab
2025-11-03 18:17 ` |FAILURE| " dpdklab
2025-11-03 18:18 ` dpdklab
2025-11-03 18:21 ` dpdklab
2025-11-03 18:22 ` dpdklab
2025-11-03 18:24 ` dpdklab
2025-11-03 18:25 ` dpdklab
2025-11-03 18:31 ` dpdklab
2025-11-03 18:41 ` |PENDING| " dpdklab
2025-11-03 18:53 ` |SUCCESS| " dpdklab
2025-11-03 18:57 ` 0-day Robot [this message]
2025-11-03 18:59 ` dpdklab
2025-11-03 19:00 ` |FAILURE| " dpdklab
2025-11-03 19:00 ` dpdklab
2025-11-03 19:09 ` dpdklab
2025-11-03 19:09 ` dpdklab
2025-11-03 22:17 ` |WARNING| " dpdklab
2025-11-04 0:03 ` |FAILURE| " 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=20251103185751.539590-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=stephen@networkplumber.org \
--cc=test-report@dpdk.org \
/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).