From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw137358 [PATCH] net/mlx5: fix the HWS registers initialization
Date: Tue, 27 Feb 2024 11:25:04 -0500 [thread overview]
Message-ID: <20240227162504.2372728-1-robot@bytheb.org> (raw)
In-Reply-To: <20240227152627.25749-1-bingz@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/137358/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8067478512
next prev parent reply other threads:[~2024-02-27 16:25 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227152627.25749-1-bingz@nvidia.com>
2024-02-27 15:04 ` qemudev
2024-02-27 15:08 ` qemudev
2024-02-27 15:28 ` checkpatch
2024-02-27 16:25 ` 0-day Robot [this message]
2024-02-27 19:43 ` |SUCCESS| pw137358 [PATCH] net/mlx5: fix the HWS registers initializ dpdklab
2024-02-27 19:46 ` dpdklab
2024-02-27 19:58 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:15 ` dpdklab
2024-02-27 20:15 ` dpdklab
2024-02-27 20:16 ` dpdklab
2024-02-27 20:23 ` dpdklab
2024-02-27 20:23 ` dpdklab
2024-02-27 20:38 ` dpdklab
2024-02-27 20:39 ` dpdklab
2024-02-27 20:42 ` dpdklab
2024-02-27 20:42 ` dpdklab
2024-02-27 20:43 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 23:21 ` dpdklab
2024-02-27 23:23 ` dpdklab
2024-02-27 23:24 ` dpdklab
2024-02-27 23:26 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:29 ` dpdklab
2024-02-27 23:29 ` dpdklab
2024-02-27 23:29 ` dpdklab
2024-02-27 23:30 ` dpdklab
2024-02-27 23:30 ` dpdklab
2024-02-27 23:31 ` dpdklab
2024-02-27 23:32 ` dpdklab
2024-02-27 23:34 ` dpdklab
2024-02-27 23:42 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:45 ` dpdklab
2024-02-27 23:45 ` dpdklab
2024-02-27 23:49 ` dpdklab
2024-02-27 23:49 ` dpdklab
2024-02-27 23:50 ` dpdklab
2024-02-27 23:50 ` dpdklab
2024-02-27 23:56 ` dpdklab
2024-02-28 0:07 ` dpdklab
2024-02-28 0:10 ` dpdklab
2024-02-28 0:32 ` dpdklab
2024-02-28 0:33 ` dpdklab
2024-02-28 0:40 ` dpdklab
2024-02-28 0:46 ` dpdklab
2024-02-28 1:00 ` dpdklab
2024-02-28 2:44 ` dpdklab
2024-02-28 2:45 ` dpdklab
2024-02-28 8:02 ` dpdklab
2024-02-28 10:38 ` dpdklab
2024-02-28 10:53 ` dpdklab
2024-02-28 17:13 ` dpdklab
2024-02-29 6:30 ` dpdklab
2024-02-29 14:13 ` dpdklab
2024-02-29 14:20 ` dpdklab
2024-02-29 14:21 ` dpdklab
2024-02-29 14:45 ` 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=20240227162504.2372728-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).