From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw137503 [PATCH v2] ethdev: add Linux ethtool link mode conversion
Date: Thu, 29 Feb 2024 11:44:58 -0500 [thread overview]
Message-ID: <20240229164458.3361521-1-robot@bytheb.org> (raw)
In-Reply-To: <20240229154343.1752555-1-thomas@monjalon.net>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/137503/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8099004968
next prev parent reply other threads:[~2024-02-29 16:45 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229154343.1752555-1-thomas@monjalon.net>
2024-02-29 15:21 ` qemudev
2024-02-29 15:25 ` qemudev
2024-02-29 15:45 ` checkpatch
2024-02-29 16:44 ` 0-day Robot [this message]
2024-02-29 19:15 ` |SUCCESS| pw137503 [PATCH] [v2] ethdev: add Linux ethtool link mode dpdklab
2024-02-29 19:19 ` dpdklab
2024-02-29 19:22 ` dpdklab
2024-02-29 19:23 ` dpdklab
2024-02-29 19:35 ` dpdklab
2024-02-29 19:37 ` dpdklab
2024-02-29 19:38 ` dpdklab
2024-02-29 19:48 ` dpdklab
2024-02-29 19:51 ` dpdklab
2024-02-29 19:51 ` dpdklab
2024-02-29 19:52 ` dpdklab
2024-02-29 19:53 ` dpdklab
2024-02-29 19:56 ` dpdklab
2024-02-29 19:59 ` dpdklab
2024-02-29 20:01 ` dpdklab
2024-02-29 20:02 ` dpdklab
2024-02-29 20:03 ` dpdklab
2024-02-29 22:52 ` dpdklab
2024-02-29 22:52 ` dpdklab
2024-02-29 22:52 ` dpdklab
2024-02-29 22:53 ` dpdklab
2024-02-29 23:02 ` dpdklab
2024-02-29 23:03 ` dpdklab
2024-02-29 23:03 ` dpdklab
2024-02-29 23:04 ` dpdklab
2024-02-29 23:04 ` dpdklab
2024-02-29 23:05 ` dpdklab
2024-02-29 23:05 ` dpdklab
2024-02-29 23:07 ` dpdklab
2024-02-29 23:07 ` dpdklab
2024-02-29 23:08 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:10 ` dpdklab
2024-02-29 23:10 ` dpdklab
2024-02-29 23:10 ` dpdklab
2024-02-29 23:11 ` dpdklab
2024-02-29 23:12 ` dpdklab
2024-02-29 23:12 ` dpdklab
2024-02-29 23:12 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-02-29 23:14 ` dpdklab
2024-02-29 23:14 ` dpdklab
2024-02-29 23:14 ` dpdklab
2024-02-29 23:19 ` dpdklab
2024-02-29 23:19 ` dpdklab
2024-02-29 23:20 ` dpdklab
2024-02-29 23:20 ` dpdklab
2024-02-29 23:33 ` dpdklab
2024-02-29 23:36 ` dpdklab
2024-02-29 23:40 ` dpdklab
2024-02-29 23:59 ` dpdklab
2024-03-01 0:00 ` dpdklab
2024-03-01 0:34 ` dpdklab
2024-03-01 6:34 ` dpdklab
2024-03-01 9:59 ` dpdklab
2024-03-01 10:05 ` dpdklab
2024-03-01 10:09 ` dpdklab
2024-03-01 10:14 ` dpdklab
2024-03-02 10:22 ` dpdklab
2024-03-03 16:07 ` dpdklab
2024-03-03 16:40 ` dpdklab
2024-03-03 17:12 ` 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=20240229164458.3361521-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).