From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw125308 [PATCH v5] net/ice: fix ice dcf control thread crash
Date: Mon, 20 Mar 2023 08:19:31 -0400 [thread overview]
Message-ID: <20230320121931.3971341-1-robot@bytheb.org> (raw)
In-Reply-To: <20230320094030.18949-1-mingjinx.ye@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/125308/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4466910202
next prev parent reply other threads:[~2023-03-20 11:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230320094030.18949-1-mingjinx.ye@intel.com>
2023-03-20 9:37 ` qemudev
2023-03-20 9:41 ` qemudev
2023-03-20 9:46 ` checkpatch
2023-03-20 12:19 ` 0-day Robot [this message]
2023-03-23 0:00 |SUCCESS| pw125308 [PATCH] [v5] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-22 22:27 dpdklab
2023-03-22 22:27 dpdklab
2023-03-22 19:03 dpdklab
2023-03-22 19:01 dpdklab
2023-03-21 8:27 dpdklab
2023-03-20 23:39 dpdklab
2023-03-20 19:24 dpdklab
2023-03-20 19:19 dpdklab
2023-03-20 16:35 dpdklab
2023-03-20 15:37 dpdklab
2023-03-20 13:08 dpdklab
2023-03-20 12:50 dpdklab
2023-03-20 12:45 dpdklab
2023-03-20 12:15 dpdklab
2023-03-20 11:54 dpdklab
2023-03-20 11:42 dpdklab
2023-03-20 11:41 dpdklab
2023-03-20 11:29 dpdklab
2023-03-20 11:23 dpdklab
2023-03-20 11:22 dpdklab
2023-03-20 11:20 dpdklab
2023-03-20 11:20 dpdklab
2023-03-20 11:18 dpdklab
2023-03-20 11:14 dpdklab
2023-03-20 11:14 dpdklab
2023-03-20 11:13 dpdklab
2023-03-20 11:10 dpdklab
2023-03-20 11:08 dpdklab
2023-03-20 11:05 dpdklab
2023-03-20 10:56 dpdklab
2023-03-20 10:56 dpdklab
2023-03-20 10:51 dpdklab
2023-03-20 10:44 dpdklab
2023-03-20 10:43 dpdklab
2023-03-20 10:42 dpdklab
2023-03-20 10:35 dpdklab
2023-03-20 10:30 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=20230320121931.3971341-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).