From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw108789 [PATCH v5] ip_frag: add IPv4 options fragment and test data
Date: Tue, 22 Mar 2022 04:11:19 +0100 (CET) [thread overview]
Message-ID: <20220322031119.D1899121CE0@dpdk.org> (raw)
In-Reply-To: <1647918560-14165-1-git-send-email-chcchc88@163.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/108789
_coding style OK_
next parent reply other threads:[~2022-03-22 3:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1647918560-14165-1-git-send-email-chcchc88@163.com>
2022-03-22 3:11 ` checkpatch [this message]
2022-03-22 5:19 ` 0-day Robot
2022-03-22 3:39 |SUCCESS| pw108789 [PATCH] [v5] " dpdklab
2022-03-22 3:40 dpdklab
2022-03-22 3:45 dpdklab
2022-03-22 3:48 dpdklab
2022-03-22 3:52 dpdklab
2022-03-22 3:55 dpdklab
2022-03-22 3:59 dpdklab
2022-03-22 4:01 dpdklab
2022-03-22 4:08 dpdklab
2022-03-22 4:08 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=20220322031119.D1899121CE0@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).