From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138374 [PATCH 3/3] net/vdev: fix insert vdev core dump
Date: Thu, 14 Mar 2024 06:43:21 -0400 [thread overview]
Message-ID: <20240314104321.1005687-1-robot@bytheb.org> (raw)
In-Reply-To: <20240314093630.1066948-4-mingjinx.ye@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138374/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8278826040
next prev parent reply other threads:[~2024-03-14 10:43 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314093630.1066948-4-mingjinx.ye@intel.com>
2024-03-14 9:32 ` |SUCCESS| pw138372-138374 " qemudev
2024-03-14 9:36 ` qemudev
2024-03-14 9:56 ` |SUCCESS| pw138374 " checkpatch
2024-03-14 10:42 ` |SUCCESS| pw138372-138374 [PATCH] [3/3] net/vdev: fix insert vdev co dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:43 ` dpdklab
2024-03-14 10:43 ` 0-day Robot [this message]
2024-03-14 10:43 ` dpdklab
2024-03-14 10:43 ` dpdklab
2024-03-14 10:44 ` dpdklab
2024-03-14 10:44 ` dpdklab
2024-03-14 10:45 ` dpdklab
2024-03-14 10:49 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:54 ` dpdklab
2024-03-14 10:54 ` dpdklab
2024-03-14 10:55 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:01 ` dpdklab
2024-03-14 11:01 ` dpdklab
2024-03-14 11:02 ` dpdklab
2024-03-14 11:10 ` dpdklab
2024-03-14 11:11 ` dpdklab
2024-03-14 11:11 ` dpdklab
2024-03-14 11:41 ` dpdklab
2024-03-14 11:42 ` dpdklab
2024-03-14 11:53 ` dpdklab
2024-03-14 11:53 ` dpdklab
2024-03-14 12:26 ` dpdklab
2024-03-18 2:33 ` dpdklab
2024-03-18 3:09 ` 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=20240314104321.1005687-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).