From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw140306 [PATCH] net/mlx5: remove redundant macro
Date: Fri, 24 May 2024 10:44:05 -0400 [thread overview]
Message-ID: <20240524144405.2619272-1-robot@bytheb.org> (raw)
In-Reply-To: <20240524134254.1496949-1-thomas@monjalon.net>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/140306/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9225252236
next prev parent reply other threads:[~2024-05-24 14:44 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240524134254.1496949-1-thomas@monjalon.net>
2024-05-24 13:21 ` qemudev
2024-05-24 13:25 ` qemudev
2024-05-24 13:43 ` checkpatch
2024-05-24 14:44 ` 0-day Robot [this message]
2024-05-24 17:17 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:18 ` dpdklab
2024-05-24 17:27 ` dpdklab
2024-05-24 17:42 ` dpdklab
2024-05-24 17:42 ` dpdklab
2024-05-24 17:42 ` dpdklab
2024-05-24 17:43 ` dpdklab
2024-05-24 17:43 ` dpdklab
2024-05-24 17:43 ` dpdklab
2024-05-24 17:44 ` dpdklab
2024-05-24 17:44 ` dpdklab
2024-05-24 17:44 ` dpdklab
2024-05-24 17:45 ` dpdklab
2024-05-24 17:45 ` dpdklab
2024-05-24 17:45 ` dpdklab
2024-05-24 17:45 ` dpdklab
2024-05-24 17:46 ` dpdklab
2024-05-24 17:46 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:47 ` dpdklab
2024-05-24 17:48 ` dpdklab
2024-05-24 17:48 ` dpdklab
2024-05-24 17:48 ` dpdklab
2024-05-24 17:48 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:49 ` dpdklab
2024-05-24 17:50 ` dpdklab
2024-05-24 17:50 ` dpdklab
2024-05-24 17:50 ` dpdklab
2024-05-24 17:50 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:51 ` dpdklab
2024-05-24 17:52 ` dpdklab
2024-05-24 17:53 ` dpdklab
2024-05-24 17:53 ` dpdklab
2024-05-24 17:54 ` dpdklab
2024-05-24 17:56 ` dpdklab
2024-05-24 17:56 ` dpdklab
2024-05-24 17:56 ` dpdklab
2024-05-24 17:57 ` dpdklab
2024-05-24 17:58 ` dpdklab
2024-05-24 17:59 ` dpdklab
2024-05-24 18:00 ` dpdklab
2024-05-24 18:00 ` dpdklab
2024-05-24 18:00 ` dpdklab
2024-05-24 18:01 ` dpdklab
2024-05-24 18:04 ` dpdklab
2024-05-24 18:05 ` dpdklab
2024-05-24 18:10 ` dpdklab
2024-05-24 18:15 ` dpdklab
2024-05-24 18:25 ` dpdklab
2024-05-24 18:30 ` dpdklab
2024-05-24 18:46 ` dpdklab
2024-05-24 18:51 ` dpdklab
2024-05-24 18:56 ` dpdklab
2024-05-24 18:58 ` 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=20240524144405.2619272-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).