From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141108 [PATCH v2 148/148] net/ice: add new device ids
Date: Wed, 12 Jun 2024 17:29:29 +0200 (CEST) [thread overview]
Message-ID: <20240612152929.51D49124124@dpdk.org> (raw)
In-Reply-To: <48213c31a15cdd7a69d18f849b68fb12275a7b5a.1718204529.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/141108
_coding style OK_
next prev parent reply other threads:[~2024-06-12 15:29 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48213c31a15cdd7a69d18f849b68fb12275a7b5a.1718204529.git.anatoly.burakov@intel.com>
2024-06-12 15:06 ` |SUCCESS| pw140961-141108 " qemudev
2024-06-12 15:11 ` qemudev
2024-06-12 15:29 ` checkpatch [this message]
2024-06-12 16:15 ` |SUCCESS| pw140961-141108 [PATCH] [v2,148/148] net/ice: add new devi dpdklab
2024-06-12 16:23 ` dpdklab
2024-06-12 16:24 ` |FAILURE| pw141108 [PATCH v2 148/148] net/ice: add new device ids 0-day Robot
2024-06-12 16:24 ` |SUCCESS| pw140961-141108 [PATCH] [v2,148/148] net/ice: add new devi dpdklab
2024-06-12 16:25 ` dpdklab
2024-06-12 16:26 ` dpdklab
2024-06-12 16:31 ` dpdklab
2024-06-13 4:22 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` |FAILURE| " dpdklab
2024-06-13 4:23 ` |SUCCESS| " dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:23 ` dpdklab
2024-06-13 4:24 ` |FAILURE| " dpdklab
2024-06-13 4:24 ` dpdklab
2024-06-13 4:24 ` dpdklab
2024-06-13 4:24 ` |SUCCESS| " dpdklab
2024-06-13 4:24 ` dpdklab
2024-06-13 4:24 ` |FAILURE| " dpdklab
2024-06-13 4:24 ` |SUCCESS| " dpdklab
2024-06-13 4:24 ` |FAILURE| " dpdklab
2024-06-13 4:24 ` |SUCCESS| " dpdklab
2024-06-13 4:24 ` dpdklab
2024-06-13 4:24 ` dpdklab
2024-06-13 4:24 ` dpdklab
2024-06-13 4:25 ` dpdklab
2024-06-13 4:25 ` dpdklab
2024-06-13 4:25 ` dpdklab
2024-06-13 4:25 ` dpdklab
2024-06-13 4:25 ` dpdklab
2024-06-13 4:25 ` dpdklab
2024-06-13 4:25 ` dpdklab
2024-06-13 4:25 ` dpdklab
2024-06-13 4:26 ` dpdklab
2024-06-13 4:26 ` dpdklab
2024-06-13 4:26 ` dpdklab
2024-06-13 4:26 ` dpdklab
2024-06-13 4:26 ` dpdklab
2024-06-13 4:26 ` dpdklab
2024-06-13 4:26 ` dpdklab
2024-06-13 4:27 ` dpdklab
2024-06-13 4:27 ` dpdklab
2024-06-13 4:27 ` dpdklab
2024-06-13 4:27 ` dpdklab
2024-06-13 4:27 ` dpdklab
2024-06-13 4:27 ` dpdklab
2024-06-13 4:28 ` dpdklab
2024-06-13 4:28 ` dpdklab
2024-06-13 4:28 ` dpdklab
2024-06-13 4:28 ` dpdklab
2024-06-13 4:28 ` dpdklab
2024-06-13 4:29 ` |FAILURE| " dpdklab
2024-06-13 4:29 ` |SUCCESS| " dpdklab
2024-06-13 4:29 ` dpdklab
2024-06-13 4:29 ` dpdklab
2024-06-13 4:29 ` dpdklab
2024-06-13 4:29 ` dpdklab
2024-06-13 4:29 ` dpdklab
2024-06-13 4:30 ` dpdklab
2024-06-13 4:30 ` |FAILURE| " dpdklab
2024-06-13 4:30 ` |SUCCESS| " dpdklab
2024-06-13 4:30 ` dpdklab
2024-06-13 4:30 ` dpdklab
2024-06-13 4:30 ` dpdklab
2024-06-13 4:30 ` dpdklab
2024-06-13 4:30 ` dpdklab
2024-06-13 4:31 ` dpdklab
2024-06-13 4:31 ` dpdklab
2024-06-13 4:31 ` dpdklab
2024-06-13 4:31 ` dpdklab
2024-06-13 4:31 ` dpdklab
2024-06-13 4:31 ` |FAILURE| " dpdklab
2024-06-13 4:31 ` |SUCCESS| " dpdklab
2024-06-13 4:31 ` dpdklab
2024-06-13 4:32 ` dpdklab
2024-06-13 4:32 ` dpdklab
2024-06-13 4:32 ` dpdklab
2024-06-13 4:32 ` dpdklab
2024-06-13 4:32 ` dpdklab
2024-06-13 4:32 ` dpdklab
2024-06-13 4:32 ` dpdklab
2024-06-13 4:32 ` dpdklab
2024-06-13 4:33 ` dpdklab
2024-06-13 4:33 ` dpdklab
2024-06-13 4:33 ` dpdklab
2024-06-13 4:34 ` dpdklab
2024-06-13 4:34 ` dpdklab
2024-06-13 4:34 ` dpdklab
2024-06-13 4:35 ` |FAILURE| " dpdklab
2024-06-13 4:35 ` |SUCCESS| " dpdklab
2024-06-13 4:35 ` dpdklab
2024-06-13 4:37 ` |FAILURE| " dpdklab
2024-06-13 4:38 ` dpdklab
2024-06-13 4:38 ` dpdklab
2024-06-13 4:40 ` dpdklab
2024-06-13 4:41 ` dpdklab
2024-06-13 4:43 ` 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=20240612152929.51D49124124@dpdk.org \
--to=checkpatch@dpdk.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).