From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142968 [PATCH v2] dts: add flow rule dataclass to testpmd shell
Date: Tue, 6 Aug 2024 18:42:48 +0200 (CEST) [thread overview]
Message-ID: <20240806164248.6CDDA123EF2@dpdk.org> (raw)
In-Reply-To: <20240806164208.3351-1-dmarx@iol.unh.edu>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/142968
_coding style OK_
next prev parent reply other threads:[~2024-08-06 16:42 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240806164208.3351-1-dmarx@iol.unh.edu>
2024-08-06 16:16 ` qemudev
2024-08-06 16:20 ` qemudev
2024-08-06 16:42 ` checkpatch [this message]
2024-08-06 17:43 ` 0-day Robot
2024-08-06 18:25 ` |PENDING| pw142968 [PATCH] [v2] dts: add flow rule dataclass to test dpdklab
2024-08-06 18:27 ` dpdklab
2024-08-06 18:28 ` dpdklab
2024-08-06 18:28 ` |SUCCESS| " dpdklab
2024-08-06 18:28 ` |PENDING| " dpdklab
2024-08-06 18:30 ` dpdklab
2024-08-06 18:30 ` dpdklab
2024-08-06 18:33 ` |SUCCESS| " dpdklab
2024-08-06 18:33 ` |PENDING| " dpdklab
2024-08-06 18:43 ` |SUCCESS| " dpdklab
2024-08-06 18:46 ` dpdklab
2024-08-06 18:47 ` |PENDING| " dpdklab
2024-08-06 18:48 ` |SUCCESS| " dpdklab
2024-08-06 18:51 ` |PENDING| " dpdklab
2024-08-06 18:55 ` dpdklab
2024-08-06 18:57 ` dpdklab
2024-08-06 18:58 ` dpdklab
2024-08-06 18:59 ` dpdklab
2024-08-06 19:01 ` dpdklab
2024-08-06 19:03 ` dpdklab
2024-08-06 19:03 ` dpdklab
2024-08-06 19:05 ` dpdklab
2024-08-06 19:07 ` dpdklab
2024-08-06 19:08 ` dpdklab
2024-08-06 19:09 ` |SUCCESS| " dpdklab
2024-08-06 19:10 ` |PENDING| " dpdklab
2024-08-06 19:11 ` dpdklab
2024-08-06 19:11 ` dpdklab
2024-08-06 19:12 ` |SUCCESS| " dpdklab
2024-08-06 19:13 ` dpdklab
2024-08-06 19:21 ` dpdklab
2024-08-06 19:22 ` dpdklab
2024-08-06 19:23 ` dpdklab
2024-08-06 19:36 ` |PENDING| " dpdklab
2024-08-06 19:42 ` |SUCCESS| " dpdklab
2024-08-06 19:47 ` dpdklab
2024-08-06 19:52 ` dpdklab
2024-08-06 19:54 ` |PENDING| " dpdklab
2024-08-06 19:56 ` |SUCCESS| " dpdklab
2024-08-06 19:57 ` |PENDING| " dpdklab
2024-08-06 19:58 ` dpdklab
2024-08-06 20:01 ` dpdklab
2024-08-06 20:07 ` dpdklab
2024-08-06 20:10 ` dpdklab
2024-08-06 20:16 ` |SUCCESS| " dpdklab
2024-08-06 20:17 ` |PENDING| " dpdklab
2024-08-06 20:18 ` dpdklab
2024-08-06 20:20 ` dpdklab
2024-08-06 20:21 ` dpdklab
2024-08-06 20:24 ` dpdklab
2024-08-06 20:24 ` dpdklab
2024-08-06 20:26 ` dpdklab
2024-08-06 20:26 ` dpdklab
2024-08-06 20:27 ` dpdklab
2024-08-06 20:27 ` dpdklab
2024-08-06 20:30 ` dpdklab
2024-08-06 20:31 ` dpdklab
2024-08-06 20:31 ` dpdklab
2024-08-06 20:32 ` dpdklab
2024-08-06 20:33 ` dpdklab
2024-08-06 20:33 ` dpdklab
2024-08-06 20:34 ` dpdklab
2024-08-06 20:34 ` dpdklab
2024-08-06 20:35 ` dpdklab
2024-08-06 20:37 ` dpdklab
2024-08-06 20:37 ` dpdklab
2024-08-06 20:39 ` dpdklab
2024-08-06 20:39 ` dpdklab
2024-08-06 20:40 ` dpdklab
2024-08-06 20:40 ` dpdklab
2024-08-06 20:41 ` dpdklab
2024-08-06 20:43 ` dpdklab
2024-08-06 20:44 ` dpdklab
2024-08-06 20:46 ` dpdklab
2024-08-06 20:49 ` dpdklab
2024-08-06 20:51 ` dpdklab
2024-08-06 20:55 ` dpdklab
2024-08-06 20:58 ` |SUCCESS| " dpdklab
2024-08-06 21:02 ` |PENDING| " dpdklab
2024-08-06 21:04 ` dpdklab
2024-08-06 21:08 ` |SUCCESS| " dpdklab
2024-08-06 21:15 ` |PENDING| " dpdklab
2024-08-06 21:16 ` dpdklab
2024-08-06 21:17 ` dpdklab
2024-08-06 21:17 ` dpdklab
2024-08-06 21:18 ` dpdklab
2024-08-06 21:19 ` dpdklab
2024-08-06 21:20 ` dpdklab
2024-08-06 21:20 ` dpdklab
2024-08-06 21:20 ` dpdklab
2024-08-06 21:21 ` dpdklab
2024-08-06 21:22 ` dpdklab
2024-08-06 21:25 ` dpdklab
2024-08-06 21:27 ` dpdklab
2024-08-06 21:28 ` dpdklab
2024-08-06 21:31 ` dpdklab
2024-08-06 21:31 ` dpdklab
2024-08-06 21:34 ` dpdklab
2024-08-06 21:45 ` dpdklab
2024-08-06 21:46 ` dpdklab
2024-08-06 21:47 ` dpdklab
2024-08-06 21:50 ` |SUCCESS| " dpdklab
2024-08-06 22:03 ` dpdklab
2024-08-07 0:24 ` dpdklab
2024-08-07 7:11 ` dpdklab
2024-08-07 7:20 ` dpdklab
2024-08-07 7:32 ` 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=20240806164248.6CDDA123EF2@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).