From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw139453 [PATCH v8 3/4] test/hash: check bulk lookup of keys after collision
Date: Wed, 17 Apr 2024 18:08:59 +0200 (CEST) [thread overview]
Message-ID: <20240417160859.1F78912083E@dpdk.org> (raw)
In-Reply-To: <20240417160807.1249480-4-yoan.picchi@arm.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/139453
_coding style OK_
parent reply other threads:[~2024-04-17 16:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240417160807.1249480-4-yoan.picchi@arm.com>]
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=20240417160859.1F78912083E@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).