From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw153590 [PATCH v3] ethdev: fix the bug where the flag variables are assigned
Date: Thu, 22 May 2025 05:03:44 -0400 [thread overview]
Message-ID: <20250522090344.1800222-1-robot@bytheb.org> (raw)
In-Reply-To: <20250522074242.30376-1-sunyang.wu@jaguarmicro.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/153590/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15181331415
next prev parent reply other threads:[~2025-05-22 9:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250522074242.30376-1-sunyang.wu@jaguarmicro.com>
2025-05-22 7:09 ` qemudev
2025-05-22 7:13 ` qemudev
2025-05-22 7:42 ` |WARNING| " checkpatch
2025-05-22 9:03 ` 0-day Robot [this message]
2025-05-22 13:07 ` |SUCCESS| pw153590 [PATCH] [v3] ethdev: fix the bug where the flag v dpdklab
2025-05-22 13:17 ` dpdklab
2025-05-22 13:18 ` dpdklab
2025-05-22 13:19 ` dpdklab
2025-05-22 13:20 ` dpdklab
2025-05-22 13:22 ` dpdklab
2025-05-22 13:31 ` dpdklab
2025-05-22 13:34 ` dpdklab
2025-05-22 14:28 ` dpdklab
2025-05-22 14:29 ` dpdklab
2025-05-22 14:31 ` dpdklab
2025-05-22 14:42 ` |WARNING| " dpdklab
2025-05-22 14:42 ` |SUCCESS| " dpdklab
2025-05-22 14:45 ` dpdklab
2025-05-22 14:48 ` dpdklab
2025-05-22 14:57 ` dpdklab
2025-05-22 15:16 ` dpdklab
2025-05-22 15:16 ` |PENDING| " dpdklab
2025-05-22 15:23 ` dpdklab
2025-05-22 15:26 ` dpdklab
2025-05-22 15:41 ` |SUCCESS| " dpdklab
2025-05-22 15:57 ` |WARNING| " dpdklab
2025-05-22 15:57 ` dpdklab
2025-05-22 16:38 ` |PENDING| " dpdklab
2025-05-22 16:41 ` dpdklab
2025-05-22 16:50 ` dpdklab
2025-05-22 16:53 ` |FAILURE| " dpdklab
2025-05-22 17:16 ` |WARNING| " dpdklab
2025-05-22 17:27 ` |SUCCESS| " dpdklab
2025-05-22 17:29 ` |FAILURE| " dpdklab
2025-05-22 17:37 ` dpdklab
2025-05-22 18:11 ` 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=20250522090344.1800222-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).