From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw149287 [PATCH] net/nfp: implement the burst mode get operation
Date: Wed, 18 Dec 2024 02:23:33 -0500 [thread overview]
Message-ID: <20241218072333.1347117-1-robot@bytheb.org> (raw)
In-Reply-To: <20241218063036.1697438-1-chaoyong.he@corigine.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/149287/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/12387800394
next prev parent reply other threads:[~2024-12-18 7:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241218063036.1697438-1-chaoyong.he@corigine.com>
2024-12-18 6:04 ` qemudev
2024-12-18 6:09 ` qemudev
2024-12-18 6:32 ` checkpatch
2024-12-18 7:23 ` 0-day Robot [this message]
2024-12-18 13:39 ` |SUCCESS| pw149287 [PATCH] net/nfp: implement the burst mode get ope dpdklab
2024-12-18 13:50 ` dpdklab
2024-12-18 13:52 ` dpdklab
2024-12-18 14:06 ` |FAILURE| " dpdklab
2024-12-18 14:08 ` |SUCCESS| " dpdklab
2024-12-18 14:16 ` dpdklab
2024-12-18 14:39 ` dpdklab
2024-12-18 14:44 ` dpdklab
2024-12-18 14:46 ` dpdklab
2024-12-18 14:57 ` dpdklab
2024-12-18 14:59 ` dpdklab
2024-12-18 15:07 ` dpdklab
2024-12-18 15:20 ` dpdklab
2024-12-18 15:24 ` dpdklab
2024-12-18 15:27 ` dpdklab
2024-12-18 15:34 ` |WARNING| " dpdklab
2024-12-18 15:34 ` dpdklab
2024-12-18 15:38 ` |SUCCESS| " dpdklab
2024-12-18 15:42 ` dpdklab
2024-12-18 15:43 ` dpdklab
2024-12-18 16:08 ` dpdklab
2024-12-18 16:10 ` dpdklab
2024-12-18 16:10 ` dpdklab
2024-12-18 16:24 ` dpdklab
2024-12-18 16:31 ` dpdklab
2024-12-18 16:38 ` dpdklab
2024-12-18 16:45 ` |WARNING| " dpdklab
2024-12-18 17:12 ` |SUCCESS| " dpdklab
2024-12-18 17:14 ` dpdklab
2024-12-18 17:23 ` dpdklab
2024-12-18 18:13 ` dpdklab
2024-12-18 20:00 ` dpdklab
2024-12-18 21:15 ` dpdklab
2024-12-19 0:05 ` |WARNING| " dpdklab
2024-12-19 0:51 ` dpdklab
2024-12-19 0:59 ` dpdklab
2024-12-19 1:17 ` 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=20241218072333.1347117-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).