From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw159617 [PATCH v2 2/2] net/null: revise info_get
Date: Tue, 6 Jan 2026 13:09:17 -0500 [thread overview]
Message-ID: <20260106180917.1497722-1-robot@bytheb.org> (raw)
In-Reply-To: <20260106164815.158430-3-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/159617/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/20755856934
next prev parent reply other threads:[~2026-01-06 18:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260106164815.158430-3-stephen@networkplumber.org>
2026-01-06 16:49 ` checkpatch
2026-01-06 17:01 ` |SUCCESS| pw159616-159617 " qemudev
2026-01-06 17:06 ` qemudev
2026-01-06 18:09 ` 0-day Robot [this message]
2026-01-06 18:09 ` |SUCCESS| pw159617 " 0-day Robot
2026-01-07 16:58 ` |SUCCESS| pw159616-159617 [PATCH] [v2,2/2] " dpdklab
2026-01-07 17:06 ` dpdklab
2026-01-07 17:07 ` |PENDING| " dpdklab
2026-01-07 17:12 ` |SUCCESS| " dpdklab
2026-01-07 17:15 ` dpdklab
2026-01-07 17:17 ` dpdklab
2026-01-07 17:38 ` dpdklab
2026-01-07 17:48 ` dpdklab
2026-01-07 21:08 ` |PENDING| " dpdklab
2026-01-08 1:40 ` |SUCCESS| " dpdklab
2026-01-08 10:14 ` dpdklab
2026-01-08 10:24 ` dpdklab
2026-01-08 10:25 ` dpdklab
2026-01-08 10:26 ` dpdklab
2026-01-08 10:27 ` dpdklab
2026-01-08 20:43 ` dpdklab
2026-01-08 21:37 ` dpdklab
2026-01-08 21:41 ` dpdklab
2026-01-08 21:49 ` dpdklab
2026-01-08 21:53 ` dpdklab
2026-01-08 21:59 ` dpdklab
2026-01-08 22:04 ` dpdklab
2026-01-08 22:05 ` dpdklab
2026-01-08 22:10 ` dpdklab
2026-01-08 22:49 ` dpdklab
2026-01-08 23:31 ` dpdklab
2026-01-08 23:48 ` dpdklab
2026-01-09 0:08 ` 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=20260106180917.1497722-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).