From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138145 [PATCH] examples/ipsec-secgw: fix Rx queue ID in Rx callback
Date: Mon, 11 Mar 2024 03:34:22 +0100 (CET) [thread overview]
Message-ID: <20240311023422.A2D601223EF@dpdk.org> (raw)
In-Reply-To: <20240311023247.2520028-1-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138145
_coding style OK_
next prev parent reply other threads:[~2024-03-11 2:34 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240311023247.2520028-1-chaoyong.he@corigine.com>
2024-03-11 2:10 ` qemudev
2024-03-11 2:14 ` qemudev
2024-03-11 2:34 ` checkpatch [this message]
2024-03-11 3:22 ` 0-day Robot
2024-03-11 7:32 ` |SUCCESS| pw138145 [PATCH] examples/ipsec-secgw: fix Rx queue ID in dpdklab
2024-03-11 7:46 ` dpdklab
2024-03-11 7:47 ` dpdklab
2024-03-11 7:48 ` dpdklab
2024-03-11 7:49 ` dpdklab
2024-03-11 7:50 ` dpdklab
2024-03-11 8:01 ` dpdklab
2024-03-11 8:02 ` dpdklab
2024-03-11 8:02 ` dpdklab
2024-03-11 8:03 ` dpdklab
2024-03-11 8:04 ` dpdklab
2024-03-11 8:04 ` dpdklab
2024-03-11 8:09 ` dpdklab
2024-03-11 8:10 ` dpdklab
2024-03-11 8:14 ` dpdklab
2024-03-11 8:16 ` dpdklab
2024-03-11 8:16 ` dpdklab
2024-03-11 8:17 ` dpdklab
2024-03-11 8:19 ` dpdklab
2024-03-11 8:19 ` dpdklab
2024-03-11 8:20 ` dpdklab
2024-03-11 8:21 ` dpdklab
2024-03-11 8:21 ` dpdklab
2024-03-11 8:21 ` dpdklab
2024-03-11 8:22 ` dpdklab
2024-03-11 8:22 ` dpdklab
2024-03-11 8:23 ` dpdklab
2024-03-11 8:23 ` dpdklab
2024-03-11 8:23 ` dpdklab
2024-03-11 8:23 ` dpdklab
2024-03-11 8:24 ` dpdklab
2024-03-11 8:24 ` dpdklab
2024-03-11 8:24 ` dpdklab
2024-03-11 8:25 ` dpdklab
2024-03-11 8:26 ` dpdklab
2024-03-11 8:26 ` dpdklab
2024-03-11 8:26 ` |FAILURE| " dpdklab
2024-03-11 8:27 ` |SUCCESS| " dpdklab
2024-03-11 8:27 ` dpdklab
2024-03-11 8:28 ` dpdklab
2024-03-11 8:28 ` |FAILURE| " dpdklab
2024-03-11 8:28 ` |SUCCESS| " dpdklab
2024-03-11 8:28 ` |FAILURE| " dpdklab
2024-03-11 8:29 ` dpdklab
2024-03-11 8:29 ` |SUCCESS| " dpdklab
2024-03-11 8:30 ` dpdklab
2024-03-11 8:30 ` |FAILURE| " dpdklab
2024-03-11 8:30 ` dpdklab
2024-03-11 8:31 ` dpdklab
2024-03-11 8:31 ` |SUCCESS| " dpdklab
2024-03-11 8:31 ` dpdklab
2024-03-11 8:31 ` dpdklab
2024-03-11 8:32 ` dpdklab
2024-03-11 8:32 ` dpdklab
2024-03-11 8:32 ` dpdklab
2024-03-11 8:32 ` |FAILURE| " dpdklab
2024-03-11 8:33 ` dpdklab
2024-03-11 8:33 ` dpdklab
2024-03-11 8:33 ` dpdklab
2024-03-11 8:33 ` |SUCCESS| " dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:34 ` dpdklab
2024-03-11 8:37 ` dpdklab
2024-03-11 8:41 ` dpdklab
2024-03-11 8:43 ` |FAILURE| " dpdklab
2024-03-11 8:44 ` |SUCCESS| " dpdklab
2024-03-11 8:52 ` dpdklab
2024-03-11 9:01 ` dpdklab
2024-03-11 9:25 ` dpdklab
2024-03-14 19:29 ` dpdklab
2024-03-14 20:16 ` 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=20240311023422.A2D601223EF@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).