From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw142557 [PATCH] net/ice: fix DCF init for E830 devices
Date: Fri, 19 Jul 2024 10:43:46 -0400 [thread overview]
Message-ID: <20240719144346.2328830-1-robot@bytheb.org> (raw)
In-Reply-To: <20240719134427.10512-1-ian.stokes@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/142557/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10009367100
next prev parent reply other threads:[~2024-07-19 14:43 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240719134427.10512-1-ian.stokes@intel.com>
2024-07-19 13:41 ` qemudev
2024-07-19 13:44 ` checkpatch
2024-07-19 13:46 ` qemudev
2024-07-19 14:43 ` 0-day Robot [this message]
2024-07-19 16:35 ` dpdklab
2024-07-19 16:39 ` dpdklab
2024-07-19 16:43 ` dpdklab
2024-07-19 16:44 ` dpdklab
2024-07-19 16:52 ` dpdklab
2024-07-19 16:56 ` dpdklab
2024-07-19 16:57 ` dpdklab
2024-07-19 16:59 ` dpdklab
2024-07-19 17:01 ` |PENDING| " dpdklab
2024-07-19 17:02 ` |SUCCESS| " dpdklab
2024-07-19 17:08 ` dpdklab
2024-07-19 17:44 ` dpdklab
2024-07-19 17:51 ` |PENDING| " dpdklab
2024-07-19 18:03 ` dpdklab
2024-07-19 18:20 ` dpdklab
2024-07-19 18:25 ` dpdklab
2024-07-19 18:35 ` dpdklab
2024-07-19 18:35 ` dpdklab
2024-07-19 18:39 ` dpdklab
2024-07-19 18:44 ` dpdklab
2024-07-19 18:52 ` dpdklab
2024-07-19 18:54 ` dpdklab
2024-07-19 18:57 ` dpdklab
2024-07-19 18:57 ` dpdklab
2024-07-19 19:00 ` dpdklab
2024-07-19 19:02 ` dpdklab
2024-07-19 19:03 ` dpdklab
2024-07-19 19:03 ` dpdklab
2024-07-19 19:03 ` dpdklab
2024-07-19 19:04 ` dpdklab
2024-07-19 19:05 ` dpdklab
2024-07-19 19:08 ` dpdklab
2024-07-19 19:11 ` dpdklab
2024-07-19 19:12 ` dpdklab
2024-07-19 19:15 ` dpdklab
2024-07-19 19:19 ` dpdklab
2024-07-19 19:22 ` dpdklab
2024-07-19 19:25 ` dpdklab
2024-07-19 19:26 ` dpdklab
2024-07-19 19:27 ` dpdklab
2024-07-19 19:28 ` dpdklab
2024-07-19 19:33 ` dpdklab
2024-07-19 19:34 ` dpdklab
2024-07-19 19:35 ` |SUCCESS| " dpdklab
2024-07-19 19:35 ` dpdklab
2024-07-19 19:36 ` |PENDING| " dpdklab
2024-07-19 19:36 ` dpdklab
2024-07-19 19:37 ` dpdklab
2024-07-19 19:39 ` dpdklab
2024-07-19 19:57 ` |SUCCESS| " dpdklab
2024-07-19 19:57 ` |PENDING| " dpdklab
2024-07-19 20:00 ` |SUCCESS| " dpdklab
2024-07-19 20:01 ` dpdklab
2024-07-19 20:02 ` |PENDING| " dpdklab
2024-07-19 20:02 ` dpdklab
2024-07-19 20:02 ` dpdklab
2024-07-19 20:05 ` dpdklab
2024-07-19 20:06 ` |SUCCESS| " dpdklab
2024-07-19 20:06 ` |PENDING| " dpdklab
2024-07-19 20:10 ` dpdklab
2024-07-19 20:10 ` dpdklab
2024-07-19 20:12 ` dpdklab
2024-07-19 20:14 ` dpdklab
2024-07-19 20:15 ` dpdklab
2024-07-19 20:15 ` dpdklab
2024-07-19 20:17 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:18 ` dpdklab
2024-07-19 20:19 ` dpdklab
2024-07-19 20:20 ` dpdklab
2024-07-19 20:20 ` dpdklab
2024-07-19 20:20 ` dpdklab
2024-07-19 20:21 ` dpdklab
2024-07-19 20:21 ` dpdklab
2024-07-19 20:21 ` dpdklab
2024-07-19 20:21 ` dpdklab
2024-07-19 20:23 ` dpdklab
2024-07-19 20:24 ` dpdklab
2024-07-19 20:24 ` dpdklab
2024-07-19 20:25 ` dpdklab
2024-07-19 20:25 ` |SUCCESS| " dpdklab
2024-07-19 20:27 ` |PENDING| " dpdklab
2024-07-19 20:27 ` dpdklab
2024-07-19 20:28 ` dpdklab
2024-07-19 20:30 ` |SUCCESS| " dpdklab
2024-07-19 20:30 ` |PENDING| " dpdklab
2024-07-19 20:30 ` dpdklab
2024-07-19 20:32 ` dpdklab
2024-07-19 20:33 ` dpdklab
2024-07-19 20:34 ` dpdklab
2024-07-19 20:37 ` dpdklab
2024-07-19 20:38 ` |SUCCESS| " dpdklab
2024-07-19 20:40 ` |PENDING| " dpdklab
2024-07-19 20:42 ` dpdklab
2024-07-19 20:45 ` dpdklab
2024-07-19 20:45 ` dpdklab
2024-07-19 20:57 ` dpdklab
2024-07-19 21:11 ` dpdklab
2024-07-19 21:20 ` dpdklab
2024-07-19 21:26 ` dpdklab
2024-07-19 21:37 ` dpdklab
2024-07-19 21:38 ` |SUCCESS| " dpdklab
2024-07-20 1:13 ` 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=20240719144346.2328830-1-robot@bytheb.org \
--to=robot@bytheb.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).