From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw133767 [PATCH v2] net/ice: fix Tx preparation
Date: Thu, 2 Nov 2023 07:03:02 +0100 (CET) [thread overview]
Message-ID: <20231102060302.B00CC120A24@dpdk.org> (raw)
In-Reply-To: <20231102142207.1510973-1-qi.z.zhang@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/133767
_coding style OK_
next prev parent reply other threads:[~2023-11-02 6:03 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231102142207.1510973-1-qi.z.zhang@intel.com>
2023-11-02 5:42 ` qemudev
2023-11-02 5:46 ` qemudev
2023-11-02 6:03 ` checkpatch [this message]
2023-11-02 7:20 ` 0-day Robot
2023-11-02 13:48 |SUCCESS| pw133767 [PATCH] [v2] " dpdklab
2023-11-02 13:48 dpdklab
2023-11-02 13:49 dpdklab
2023-11-02 13:50 dpdklab
2023-11-02 13:50 dpdklab
2023-11-02 13:50 dpdklab
2023-11-02 13:51 dpdklab
2023-11-02 13:51 dpdklab
2023-11-02 13:51 dpdklab
2023-11-02 13:52 dpdklab
2023-11-02 13:52 dpdklab
2023-11-02 13:52 dpdklab
2023-11-02 13:53 dpdklab
2023-11-02 13:53 dpdklab
2023-11-02 13:55 dpdklab
2023-11-02 13:57 dpdklab
2023-11-02 13:58 dpdklab
2023-11-02 13:58 dpdklab
2023-11-02 13:58 dpdklab
2023-11-02 13:58 dpdklab
2023-11-02 13:59 dpdklab
2023-11-02 13:59 dpdklab
2023-11-02 13:59 dpdklab
2023-11-02 13:59 dpdklab
2023-11-02 14:00 dpdklab
2023-11-02 14:00 dpdklab
2023-11-02 14:00 dpdklab
2023-11-02 14:00 dpdklab
2023-11-02 14:01 dpdklab
2023-11-02 14:01 dpdklab
2023-11-02 14:01 dpdklab
2023-11-02 14:01 dpdklab
2023-11-02 14:01 dpdklab
2023-11-02 14:01 dpdklab
2023-11-02 14:02 dpdklab
2023-11-02 14:03 dpdklab
2023-11-02 14:03 dpdklab
2023-11-02 14:04 dpdklab
2023-11-02 14:04 dpdklab
2023-11-02 14:16 dpdklab
2023-11-02 14:17 dpdklab
2023-11-02 14:26 dpdklab
2023-11-02 14:26 dpdklab
2023-11-02 14:26 dpdklab
2023-11-02 14:26 dpdklab
2023-11-02 14:26 dpdklab
2023-11-02 14:39 dpdklab
2023-11-02 14:39 dpdklab
2023-11-02 14:39 dpdklab
2023-11-02 14:42 dpdklab
2023-11-02 15:25 dpdklab
2023-11-02 21:19 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=20231102060302.B00CC120A24@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).