From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw133764 [PATCH] net/iavf: fix Tx preparation
Date: Thu, 2 Nov 2023 04:45:57 +0100 (CET) [thread overview]
Message-ID: <20231102034557.C5342120A24@dpdk.org> (raw)
In-Reply-To: <20231102120504.1468111-1-qi.z.zhang@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/133764
_coding style OK_
next prev parent reply other threads:[~2023-11-02 3:45 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231102120504.1468111-1-qi.z.zhang@intel.com>
2023-11-02 3:26 ` qemudev
2023-11-02 3:30 ` qemudev
2023-11-02 3:45 ` checkpatch [this message]
2023-11-02 4:39 ` 0-day Robot
2023-11-02 5:40 dpdklab
2023-11-02 5:45 dpdklab
2023-11-02 5:50 dpdklab
2023-11-02 5:54 dpdklab
2023-11-02 5:55 dpdklab
2023-11-02 5:55 dpdklab
2023-11-02 5:57 dpdklab
2023-11-02 6:00 dpdklab
2023-11-02 7:08 dpdklab
2023-11-02 7:12 dpdklab
2023-11-02 7:12 dpdklab
2023-11-02 7:17 dpdklab
2023-11-02 7:18 dpdklab
2023-11-02 7:18 dpdklab
2023-11-02 7:18 dpdklab
2023-11-02 7:19 dpdklab
2023-11-02 7:24 dpdklab
2023-11-02 7:27 dpdklab
2023-11-02 7:27 dpdklab
2023-11-02 7:28 dpdklab
2023-11-02 7:30 dpdklab
2023-11-02 7:30 dpdklab
2023-11-02 7:30 dpdklab
2023-11-02 7:32 dpdklab
2023-11-02 7:32 dpdklab
2023-11-02 7:32 dpdklab
2023-11-02 7:32 dpdklab
2023-11-02 7:32 dpdklab
2023-11-02 7:33 dpdklab
2023-11-02 7:34 dpdklab
2023-11-02 7:35 dpdklab
2023-11-02 7:37 dpdklab
2023-11-02 7:38 dpdklab
2023-11-02 7:38 dpdklab
2023-11-02 7:39 dpdklab
2023-11-02 7:39 dpdklab
2023-11-02 7:40 dpdklab
2023-11-02 7:41 dpdklab
2023-11-02 7:41 dpdklab
2023-11-02 7:42 dpdklab
2023-11-02 7:43 dpdklab
2023-11-02 7:43 dpdklab
2023-11-02 7:44 dpdklab
2023-11-02 7:44 dpdklab
2023-11-02 7:46 dpdklab
2023-11-02 8:00 dpdklab
2023-11-02 8:03 dpdklab
2023-11-02 8:06 dpdklab
2023-11-02 8:21 dpdklab
2023-11-02 9:57 dpdklab
2023-11-02 10:41 dpdklab
2023-11-02 19:58 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=20231102034557.C5342120A24@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).