From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Krzysztof Karas <krzysztof.karas@intel.com>
Subject: |WARNING| pw134130 [PATCH v2] crypto/ipsec_mb: do not dequeue ops after flush
Date: Mon, 13 Nov 2023 09:04:50 +0100 (CET) [thread overview]
Message-ID: <20231113080450.C551F120DB4@dpdk.org> (raw)
In-Reply-To: <20231113080158.3872440-1-krzysztof.karas@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/134130
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
next prev parent reply other threads:[~2023-11-13 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231113080158.3872440-1-krzysztof.karas@intel.com>
2023-11-13 7:45 ` |SUCCESS| " qemudev
2023-11-13 7:49 ` qemudev
2023-11-13 8:04 ` checkpatch [this message]
2023-11-13 8:59 ` 0-day Robot
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=20231113080450.C551F120DB4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=krzysztof.karas@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).