From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw112586 [PATCH v1] ip_frag: add IPv4 fragment copy packet API
Date: Thu, 9 Jun 2022 04:40:34 +0200 (CEST) [thread overview]
Message-ID: <20220609024034.AD589123450@dpdk.org> (raw)
In-Reply-To: <1654742388-3377-1-git-send-email-chcchc88@163.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/112586
_coding style OK_
next parent reply other threads:[~2022-06-09 2:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1654742388-3377-1-git-send-email-chcchc88@163.com>
2022-06-09 2:40 ` checkpatch [this message]
2022-06-09 3:59 ` |FAILURE| " 0-day Robot
2022-06-11 11:56 |SUCCESS| pw112586 [PATCH] [v1] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-06-09 5:57 dpdklab
2022-06-09 5:57 dpdklab
2022-06-09 5:35 dpdklab
2022-06-09 5:28 dpdklab
2022-06-09 3:59 dpdklab
2022-06-09 3:53 dpdklab
2022-06-09 3:52 dpdklab
2022-06-09 3:35 dpdklab
2022-06-09 3:34 dpdklab
2022-06-09 3:28 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=20220609024034.AD589123450@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).