automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw125135 [PATCH v3] net/ice: fix ice dcf control thread crash
Date: Wed, 15 Mar 2023 06:39:27 -0400	[thread overview]
Message-ID: <20230315103927.3022170-1-robot@bytheb.org> (raw)
In-Reply-To: <20230315082018.4260-1-mingjinx.ye@intel.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/125135/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4424338854

  parent reply	other threads:[~2023-03-15  9:39 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230315082018.4260-1-mingjinx.ye@intel.com>
2023-03-15  8:14 ` qemudev
2023-03-15  8:18 ` qemudev
2023-03-15  8:26 ` checkpatch
2023-03-15 10:39 ` 0-day Robot [this message]
2023-03-15  9:14 |SUCCESS| pw125135 [PATCH] [v3] " dpdklab
2023-03-15  9:24 dpdklab
2023-03-15  9:26 dpdklab
2023-03-15  9:34 dpdklab
2023-03-15  9:34 dpdklab
2023-03-15  9:36 dpdklab
2023-03-15  9:40 dpdklab
2023-03-15  9:41 dpdklab
2023-03-15  9:41 dpdklab
2023-03-15  9:45 dpdklab
2023-03-15  9:47 dpdklab
2023-03-15  9:47 dpdklab
2023-03-15  9:47 dpdklab
2023-03-15  9:49 dpdklab
2023-03-15  9:56 dpdklab
2023-03-15  9:56 dpdklab
2023-03-15  9:58 dpdklab
2023-03-15 10:00 dpdklab
2023-03-15 10:01 dpdklab
2023-03-15 10:01 dpdklab
2023-03-15 10:05 dpdklab
2023-03-15 10:10 dpdklab
2023-03-15 10:12 dpdklab
2023-03-15 10:13 dpdklab
2023-03-15 10:25 dpdklab
2023-03-15 10:30 dpdklab
2023-03-15 10:43 dpdklab
2023-03-15 10:45 dpdklab
2023-03-15 10:46 dpdklab
2023-03-15 11:03 dpdklab
2023-03-15 11:04 dpdklab
2023-03-15 11:52 dpdklab
2023-03-17 12:45 dpdklab
2023-03-17 13:44 dpdklab
2023-03-17 18:49 dpdklab
2023-03-18  2:06 dpdklab
2023-03-18  4:53 dpdklab
2023-03-18  7:48 dpdklab
2023-03-18 12:55 dpdklab
2023-03-18 12:59 dpdklab
2023-03-18 13:02 dpdklab
2023-03-18 13:11 dpdklab
2023-03-18 13:16 dpdklab
2023-03-18 13:16 dpdklab
2023-03-18 13:18 dpdklab
2023-03-18 13:24 dpdklab
2023-03-18 13:28 dpdklab
2023-03-18 13:31 dpdklab
2023-03-18 13:31 dpdklab
2023-03-18 20:15 dpdklab
2023-03-18 20:21 dpdklab
2023-03-18 20:23 dpdklab
2023-03-18 20:25 dpdklab
2023-03-18 20:29 dpdklab
2023-03-18 20:39 dpdklab
2023-03-18 20:40 dpdklab
2023-03-18 20:41 dpdklab
2023-03-18 20:45 dpdklab
2023-03-18 20:51 dpdklab
2023-03-18 20:56 dpdklab
2023-03-18 20:57 dpdklab
2023-03-18 20:57 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=20230315103927.3022170-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).