From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw153803 [PATCH] common/mlx5: avoid warning about operation mixing different enum types
Date: Tue, 27 May 2025 21:04:39 -0400 [thread overview]
Message-ID: <20250528010439.2251793-1-robot@bytheb.org> (raw)
In-Reply-To: <1748389285-26763-1-git-send-email-andremue@linux.microsoft.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/153803/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15288344892
next prev parent reply other threads:[~2025-05-28 1:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1748389285-26763-1-git-send-email-andremue@linux.microsoft.com>
2025-05-27 23:07 ` qemudev
2025-05-27 23:11 ` qemudev
2025-05-27 23:41 ` checkpatch
2025-05-28 1:04 ` 0-day Robot [this message]
2025-05-30 3:47 ` |SUCCESS| pw153803 [PATCH] common/mlx5: avoid warning about operatio dpdklab
2025-05-30 4:08 ` dpdklab
2025-05-30 5:49 ` |PENDING| " dpdklab
2025-05-30 5:55 ` |SUCCESS| " dpdklab
2025-05-30 5:57 ` |PENDING| " dpdklab
2025-05-30 6:09 ` dpdklab
2025-05-30 6:43 ` |SUCCESS| " dpdklab
2025-05-30 6:54 ` dpdklab
2025-05-30 7:01 ` |PENDING| " dpdklab
2025-05-30 9:16 ` |WARNING| " dpdklab
2025-05-30 9:17 ` dpdklab
2025-05-30 9:17 ` dpdklab
2025-05-30 9:20 ` dpdklab
2025-05-30 9:20 ` dpdklab
2025-05-30 9:20 ` dpdklab
2025-05-30 9:21 ` dpdklab
2025-05-30 9:22 ` dpdklab
2025-05-30 9:23 ` dpdklab
2025-05-30 9:23 ` dpdklab
2025-05-30 9:30 ` dpdklab
2025-05-30 12:51 ` |SUCCESS| " dpdklab
2025-05-30 13:22 ` |WARNING| " dpdklab
2025-05-30 22:47 ` dpdklab
2025-05-30 22:49 ` dpdklab
2025-05-31 3:36 ` |SUCCESS| " dpdklab
2025-05-31 4:38 ` |FAILURE| " dpdklab
2025-05-31 5:09 ` dpdklab
2025-06-04 14:55 ` |SUCCESS| " 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=20250528010439.2251793-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).