From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138653 [PATCH] net/nfp: fix receive packets failed
Date: Thu, 21 Mar 2024 07:57:50 +0100 (CET) [thread overview]
Message-ID: <20240321065750.C87771223F9@dpdk.org> (raw)
In-Reply-To: <20240321065639.301075-1-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138653
_coding style OK_
next prev parent reply other threads:[~2024-03-21 6:57 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240321065639.301075-1-chaoyong.he@corigine.com>
2024-03-21 6:35 ` qemudev
2024-03-21 6:40 ` qemudev
2024-03-21 6:57 ` checkpatch [this message]
2024-03-21 7:45 ` 0-day Robot
2024-03-21 9:57 ` dpdklab
2024-03-21 10:07 ` dpdklab
2024-03-21 10:07 ` dpdklab
2024-03-21 10:07 ` dpdklab
2024-03-21 10:08 ` dpdklab
2024-03-21 10:09 ` dpdklab
2024-03-21 10:09 ` dpdklab
2024-03-21 10:09 ` dpdklab
2024-03-21 10:12 ` dpdklab
2024-03-21 10:13 ` dpdklab
2024-03-21 10:13 ` dpdklab
2024-03-21 10:15 ` dpdklab
2024-03-21 10:32 ` dpdklab
2024-03-21 10:38 ` dpdklab
2024-03-21 10:38 ` dpdklab
2024-03-21 10:40 ` dpdklab
2024-03-21 10:40 ` dpdklab
2024-03-21 10:41 ` dpdklab
2024-03-21 10:55 ` dpdklab
2024-03-21 10:55 ` dpdklab
2024-03-21 10:55 ` dpdklab
2024-03-21 11:19 ` dpdklab
2024-03-21 11:21 ` dpdklab
2024-03-21 11:21 ` dpdklab
2024-03-21 11:22 ` dpdklab
2024-03-21 11:22 ` dpdklab
2024-03-21 11:23 ` dpdklab
2024-03-21 11:23 ` dpdklab
2024-03-21 11:23 ` dpdklab
2024-03-21 11:23 ` dpdklab
2024-03-21 11:25 ` dpdklab
2024-03-21 11:26 ` dpdklab
2024-03-21 11:26 ` dpdklab
2024-03-21 11:27 ` dpdklab
2024-03-21 11:28 ` dpdklab
2024-03-21 11:38 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:40 ` dpdklab
2024-03-21 11:41 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:43 ` dpdklab
2024-03-21 11:43 ` dpdklab
2024-03-21 11:43 ` dpdklab
2024-03-21 11:44 ` dpdklab
2024-03-21 11:45 ` dpdklab
2024-03-21 11:50 ` dpdklab
2024-03-21 11:50 ` dpdklab
2024-03-21 11:51 ` dpdklab
2024-03-21 11:51 ` dpdklab
2024-03-21 11:51 ` dpdklab
2024-03-21 11:51 ` dpdklab
2024-03-21 11:52 ` dpdklab
2024-03-21 11:52 ` dpdklab
2024-03-21 12:13 ` dpdklab
2024-03-21 12:14 ` dpdklab
2024-03-21 12:15 ` dpdklab
2024-03-21 12:24 ` dpdklab
2024-03-21 12:25 ` dpdklab
2024-03-21 12:32 ` dpdklab
2024-03-21 12:33 ` dpdklab
2024-03-21 12:34 ` dpdklab
2024-03-21 12:34 ` dpdklab
2024-03-21 12:35 ` dpdklab
2024-03-21 12:38 ` dpdklab
2024-03-21 12:42 ` dpdklab
2024-03-21 12:43 ` dpdklab
2024-03-21 12:44 ` dpdklab
2024-03-21 12:44 ` dpdklab
2024-03-21 12:45 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:53 ` dpdklab
2024-03-21 15:08 ` dpdklab
2024-03-21 15:23 ` dpdklab
2024-03-21 23:58 ` dpdklab
2024-03-23 6:02 ` dpdklab
2024-03-23 6:47 ` 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=20240321065750.C87771223F9@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).