From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kai Ji <kai.ji@intel.com>
Subject: |WARNING| pw157035 [dpdk-dev v4 2/2] crypto/ipsec-mb: use constant-time memory comparison
Date: Mon, 29 Sep 2025 16:49:02 +0200 (CEST) [thread overview]
Message-ID: <20250929144902.D0C41124247@dpdk.org> (raw)
In-Reply-To: <20250929145049.153078-2-kai.ji@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/157035
_coding style issues_
WARNING:MISSING_FIXES_TAG: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag?
total: 0 errors, 1 warnings, 61 lines checked
next prev parent reply other threads:[~2025-09-29 14:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250929145049.153078-2-kai.ji@intel.com>
2025-09-29 14:17 ` |SUCCESS| pw157034-157035 " qemudev
2025-09-29 14:22 ` qemudev
2025-09-29 14:49 ` checkpatch [this message]
2025-09-29 15:27 ` |PENDING| pw157034-157035 [PATCH] [v4,2/2] crypto/ipsec-mb: use cons dpdklab
2025-09-29 15:27 ` |SUCCESS| " dpdklab
2025-09-29 15:31 ` dpdklab
2025-09-29 15:46 ` dpdklab
2025-09-29 15:48 ` |PENDING| " dpdklab
2025-09-29 16:01 ` dpdklab
2025-09-29 16:03 ` |SUCCESS| " dpdklab
2025-09-29 16:21 ` dpdklab
2025-09-29 16:22 ` dpdklab
2025-09-29 16:57 ` |FAILURE| pw157035 [dpdk-dev v4 2/2] crypto/ipsec-mb: use constant-time memory comparison 0-day Robot
2025-09-29 17:08 ` |SUCCESS| pw157034-157035 [PATCH] [v4,2/2] crypto/ipsec-mb: use cons dpdklab
2025-09-29 17:15 ` dpdklab
2025-09-29 17:19 ` dpdklab
2025-09-29 17:20 ` dpdklab
2025-09-29 17:20 ` |PENDING| " dpdklab
2025-09-29 17:20 ` |SUCCESS| " dpdklab
2025-09-29 17:20 ` dpdklab
2025-09-29 18:56 ` dpdklab
2025-09-30 0:18 ` dpdklab
2025-09-30 4:35 ` dpdklab
2025-09-30 4:35 ` dpdklab
2025-09-30 4:35 ` dpdklab
2025-10-01 5:00 ` 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=20250929144902.D0C41124247@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kai.ji@intel.com \
--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).