From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138732 [PATCH] maintainers: update for gve/igc/ntb drivers
Date: Fri, 22 Mar 2024 03:05:01 -0400 [thread overview]
Message-ID: <20240322070501.405861-1-robot@bytheb.org> (raw)
In-Reply-To: <20240322135959.345397-1-junfeng.guo@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138732/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8386389465
next prev parent reply other threads:[~2024-03-22 7:05 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240322135959.345397-1-junfeng.guo@intel.com>
2024-03-22 5:41 ` qemudev
2024-03-22 5:46 ` qemudev
2024-03-22 6:05 ` checkpatch
2024-03-22 6:54 ` |SUCCESS| pw138732 [PATCH] maintainers: update for gve/igc/ntb drive dpdklab
2024-03-22 6:57 ` dpdklab
2024-03-22 7:02 ` dpdklab
2024-03-22 7:03 ` dpdklab
2024-03-22 7:03 ` dpdklab
2024-03-22 7:04 ` dpdklab
2024-03-22 7:04 ` dpdklab
2024-03-22 7:05 ` 0-day Robot [this message]
2024-03-22 7:05 ` dpdklab
2024-03-22 7:06 ` dpdklab
2024-03-22 7:06 ` dpdklab
2024-03-22 7:06 ` dpdklab
2024-03-22 7:06 ` dpdklab
2024-03-22 7:06 ` dpdklab
2024-03-22 7:07 ` dpdklab
2024-03-22 7:07 ` dpdklab
2024-03-22 7:07 ` dpdklab
2024-03-22 7:11 ` dpdklab
2024-03-22 7:11 ` dpdklab
2024-03-22 7:12 ` dpdklab
2024-03-22 7:19 ` dpdklab
2024-03-22 7:20 ` dpdklab
2024-03-22 7:20 ` dpdklab
2024-03-22 7:20 ` dpdklab
2024-03-22 7:21 ` dpdklab
2024-03-22 7:21 ` dpdklab
2024-03-22 7:21 ` dpdklab
2024-03-22 7:21 ` dpdklab
2024-03-22 7:22 ` dpdklab
2024-03-22 7:22 ` dpdklab
2024-03-22 7:26 ` dpdklab
2024-03-22 7:26 ` dpdklab
2024-03-22 7:27 ` dpdklab
2024-03-22 7:27 ` dpdklab
2024-03-22 7:27 ` dpdklab
2024-03-22 7:28 ` dpdklab
2024-03-22 7:28 ` dpdklab
2024-03-22 7:28 ` dpdklab
2024-03-22 7:30 ` dpdklab
2024-03-22 7:30 ` dpdklab
2024-03-22 7:31 ` dpdklab
2024-03-22 7:32 ` dpdklab
2024-03-22 7:32 ` dpdklab
2024-03-22 7:33 ` dpdklab
2024-03-22 7:33 ` dpdklab
2024-03-22 7:34 ` dpdklab
2024-03-22 7:34 ` dpdklab
2024-03-22 7:34 ` dpdklab
2024-03-22 7:35 ` dpdklab
2024-03-22 7:35 ` dpdklab
2024-03-22 7:35 ` dpdklab
2024-03-22 7:37 ` dpdklab
2024-03-22 7:37 ` dpdklab
2024-03-22 7:37 ` dpdklab
2024-03-22 7:37 ` dpdklab
2024-03-22 7:38 ` dpdklab
2024-03-22 7:40 ` dpdklab
2024-03-22 7:40 ` dpdklab
2024-03-22 7:40 ` dpdklab
2024-03-22 7:41 ` dpdklab
2024-03-22 7:43 ` dpdklab
2024-03-22 7:45 ` dpdklab
2024-03-22 7:46 ` dpdklab
2024-03-22 7:47 ` dpdklab
2024-03-22 7:48 ` dpdklab
2024-03-22 7:49 ` dpdklab
2024-03-22 7:54 ` dpdklab
2024-03-22 7:55 ` dpdklab
2024-03-22 7:56 ` dpdklab
2024-03-22 7:57 ` dpdklab
2024-03-22 7:57 ` dpdklab
2024-03-22 8:10 ` dpdklab
2024-03-22 8:22 ` dpdklab
2024-03-22 8:32 ` dpdklab
2024-03-24 0:08 ` dpdklab
2024-03-24 0:44 ` 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=20240322070501.405861-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).