From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137458 [PATCH v3] lib/hash: add siphash
Date: Thu, 29 Feb 2024 01:33:56 +0100 (CET) [thread overview]
Message-ID: <20240229003356.44F6C122320@dpdk.org> (raw)
In-Reply-To: <20240229003201.186997-2-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/137458
_coding style OK_
next prev parent reply other threads:[~2024-02-29 0:34 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229003201.186997-2-stephen@networkplumber.org>
2024-02-29 0:10 ` qemudev
2024-02-29 0:15 ` qemudev
2024-02-29 0:33 ` checkpatch [this message]
2024-02-29 1:08 ` |SUCCESS| pw137458 [PATCH] [v3] " dpdklab
2024-02-29 1:08 ` dpdklab
2024-02-29 1:08 ` dpdklab
2024-02-29 1:08 ` dpdklab
2024-02-29 1:08 ` dpdklab
2024-02-29 1:09 ` dpdklab
2024-02-29 1:09 ` dpdklab
2024-02-29 1:09 ` dpdklab
2024-02-29 1:10 ` dpdklab
2024-02-29 1:10 ` dpdklab
2024-02-29 1:10 ` dpdklab
2024-02-29 1:11 ` dpdklab
2024-02-29 1:11 ` dpdklab
2024-02-29 1:11 ` dpdklab
2024-02-29 1:12 ` dpdklab
2024-02-29 1:12 ` dpdklab
2024-02-29 1:12 ` dpdklab
2024-02-29 1:12 ` dpdklab
2024-02-29 1:13 ` dpdklab
2024-02-29 1:13 ` dpdklab
2024-02-29 1:13 ` dpdklab
2024-02-29 1:13 ` dpdklab
2024-02-29 1:14 ` dpdklab
2024-02-29 1:14 ` dpdklab
2024-02-29 1:15 ` dpdklab
2024-02-29 1:15 ` dpdklab
2024-02-29 1:15 ` dpdklab
2024-02-29 1:15 ` dpdklab
2024-02-29 1:16 ` dpdklab
2024-02-29 1:16 ` dpdklab
2024-02-29 1:17 ` dpdklab
2024-02-29 1:17 ` dpdklab
2024-02-29 1:23 ` dpdklab
2024-02-29 1:23 ` dpdklab
2024-02-29 1:25 ` |SUCCESS| pw137458 [PATCH v3] " 0-day Robot
2024-02-29 1:25 ` |SUCCESS| pw137458 [PATCH] [v3] " dpdklab
2024-02-29 1:26 ` dpdklab
2024-02-29 1:26 ` dpdklab
2024-02-29 1:26 ` dpdklab
2024-02-29 1:26 ` dpdklab
2024-02-29 1:26 ` dpdklab
2024-02-29 1:27 ` dpdklab
2024-02-29 1:28 ` dpdklab
2024-02-29 1:28 ` dpdklab
2024-02-29 1:28 ` dpdklab
2024-02-29 1:29 ` dpdklab
2024-02-29 1:29 ` dpdklab
2024-02-29 1:29 ` dpdklab
2024-02-29 1:30 ` dpdklab
2024-02-29 1:30 ` dpdklab
2024-02-29 1:34 ` dpdklab
2024-02-29 1:37 ` dpdklab
2024-02-29 1:44 ` dpdklab
2024-02-29 1:44 ` dpdklab
2024-02-29 1:44 ` dpdklab
2024-02-29 1:44 ` dpdklab
2024-02-29 1:44 ` dpdklab
2024-02-29 1:45 ` dpdklab
2024-02-29 1:50 ` dpdklab
2024-02-29 1:52 ` dpdklab
2024-02-29 1:52 ` dpdklab
2024-02-29 1:53 ` dpdklab
2024-02-29 1:53 ` dpdklab
2024-02-29 1:54 ` dpdklab
2024-02-29 2:40 ` dpdklab
2024-03-01 1:30 ` dpdklab
2024-03-01 1:32 ` dpdklab
2024-03-01 1:42 ` dpdklab
2024-03-01 1:45 ` dpdklab
2024-03-01 10:17 ` |WARNING| " dpdklab
2024-03-02 6:58 ` |SUCCESS| " dpdklab
2024-03-02 7:30 ` dpdklab
2024-03-02 8:02 ` |WARNING| " dpdklab
2024-03-02 21:19 ` |SUCCESS| " 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=20240229003356.44F6C122320@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).