From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw95966 [PATCH v2] net/mlx5: do not allow copy to mark via modify field
Date: Fri, 16 Jul 2021 10:44:04 +0200 (CEST) [thread overview]
Message-ID: <20210716084404.3EA5B120F1F@dpdk.org> (raw)
In-Reply-To: <20210716084305.646731-1-akozyrev@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/95966
_coding style OK_
next parent reply other threads:[~2021-07-16 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210716084305.646731-1-akozyrev@nvidia.com>
2021-07-16 8:44 ` checkpatch [this message]
2021-07-16 9:19 ` [dpdk-test-report] |SUCCESS| pw95966 [dpdk-dev] " 0-day Robot
2021-07-19 16:01 [dpdk-test-report] |SUCCESS| pw95966 [PATCH] [v2] " dpdklab
2021-07-19 16:17 dpdklab
2021-07-19 16:36 dpdklab
2021-07-19 17:14 dpdklab
2021-07-21 5:02 dpdklab
2021-07-21 5:18 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=20210716084404.3EA5B120F1F@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).