From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw139110 [PATCH v11 4/4] cryptodev: remove rte marker fields
Date: Thu, 4 Apr 2024 19:52:50 +0200 (CEST) [thread overview]
Message-ID: <20240404175250.D6B00121EEE@dpdk.org> (raw)
In-Reply-To: <1712253115-8755-5-git-send-email-roretzla@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/139110
_coding style OK_
next prev parent reply other threads:[~2024-04-04 17:52 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1712253115-8755-5-git-send-email-roretzla@linux.microsoft.com>
2024-04-04 17:30 ` |SUCCESS| pw139107-139110 " qemudev
2024-04-04 17:35 ` qemudev
2024-04-04 17:52 ` checkpatch [this message]
2024-04-04 18:41 ` |SUCCESS| pw139107-139110 [PATCH] [v11,4/4] cryptodev: remove rte ma dpdklab
2024-04-04 18:44 ` |SUCCESS| pw139110 [PATCH v11 4/4] cryptodev: remove rte marker fields 0-day Robot
2024-04-04 18:45 ` |SUCCESS| pw139107-139110 [PATCH] [v11,4/4] cryptodev: remove rte ma dpdklab
2024-04-04 18:46 ` dpdklab
2024-04-04 18:46 ` dpdklab
2024-04-04 18:47 ` dpdklab
2024-04-04 18:47 ` dpdklab
2024-04-04 18:47 ` dpdklab
2024-04-04 18:48 ` dpdklab
2024-04-04 18:48 ` dpdklab
2024-04-04 18:48 ` dpdklab
2024-04-04 18:51 ` dpdklab
2024-04-04 18:52 ` |WARNING| " dpdklab
2024-04-04 18:52 ` |SUCCESS| " dpdklab
2024-04-04 18:52 ` dpdklab
2024-04-04 18:52 ` dpdklab
2024-04-04 18:53 ` dpdklab
2024-04-04 18:53 ` |WARNING| " dpdklab
2024-04-04 18:53 ` |SUCCESS| " dpdklab
2024-04-04 18:54 ` dpdklab
2024-04-04 18:54 ` |WARNING| " dpdklab
2024-04-04 18:54 ` dpdklab
2024-04-04 18:58 ` dpdklab
2024-04-04 18:59 ` |SUCCESS| " dpdklab
2024-04-04 18:59 ` |WARNING| " dpdklab
2024-04-04 19:00 ` dpdklab
2024-04-04 19:00 ` |SUCCESS| " dpdklab
2024-04-04 19:00 ` |WARNING| " dpdklab
2024-04-04 19:01 ` dpdklab
2024-04-04 19:01 ` dpdklab
2024-04-04 19:16 ` dpdklab
2024-04-04 19:23 ` |SUCCESS| " dpdklab
2024-04-04 19:23 ` dpdklab
2024-04-04 19:24 ` dpdklab
2024-04-04 19:31 ` dpdklab
2024-04-04 19:31 ` dpdklab
2024-04-04 19:32 ` dpdklab
2024-04-04 19:32 ` dpdklab
2024-04-04 19:33 ` dpdklab
2024-04-04 19:33 ` dpdklab
2024-04-04 19:33 ` dpdklab
2024-04-04 19:33 ` dpdklab
2024-04-04 19:34 ` dpdklab
2024-04-04 19:34 ` dpdklab
2024-04-04 19:35 ` dpdklab
2024-04-04 19:35 ` dpdklab
2024-04-04 19:36 ` dpdklab
2024-04-04 19:36 ` dpdklab
2024-04-04 19:37 ` dpdklab
2024-04-04 19:46 ` dpdklab
2024-04-04 19:47 ` dpdklab
2024-04-04 19:50 ` dpdklab
2024-04-04 19:55 ` dpdklab
2024-04-04 19:55 ` dpdklab
2024-04-04 19:56 ` dpdklab
2024-04-04 19:57 ` dpdklab
2024-04-04 19:57 ` dpdklab
2024-04-04 19:57 ` dpdklab
2024-04-04 19:58 ` dpdklab
2024-04-04 19:58 ` dpdklab
2024-04-04 19:58 ` dpdklab
2024-04-04 19:59 ` dpdklab
2024-04-04 20:00 ` dpdklab
2024-04-04 20:00 ` dpdklab
2024-04-04 20:01 ` dpdklab
2024-04-04 20:02 ` dpdklab
2024-04-04 20:02 ` dpdklab
2024-04-04 20:03 ` dpdklab
2024-04-04 20:03 ` dpdklab
2024-04-04 20:04 ` dpdklab
2024-04-04 20:04 ` dpdklab
2024-04-04 20:06 ` dpdklab
2024-04-04 20:07 ` dpdklab
2024-04-04 20:11 ` dpdklab
2024-04-04 20:18 ` dpdklab
2024-04-04 20:22 ` dpdklab
2024-04-04 20:25 ` dpdklab
2024-04-04 20:25 ` dpdklab
2024-04-04 20:35 ` dpdklab
2024-04-04 20:38 ` dpdklab
2024-04-04 20:51 ` dpdklab
2024-04-04 20:55 ` dpdklab
2024-04-04 21:36 ` dpdklab
2024-04-04 22:06 ` dpdklab
2024-04-04 22:16 ` dpdklab
2024-04-04 22:39 ` dpdklab
2024-04-04 22:46 ` dpdklab
2024-04-04 22:50 ` dpdklab
2024-04-04 22:54 ` dpdklab
2024-04-04 22: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=20240404175250.D6B00121EEE@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).