From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw106013 [PATCH] net/mlx5: reject jump to root table
Date: Tue, 18 Jan 2022 12:40:45 +0100 (CET) [thread overview]
Message-ID: <20220118114046.0329D12091F@dpdk.org> (raw)
In-Reply-To: <798beef100ce147f20e03f7590c7770e56a246cc.1642505511.git.jackmin@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/106013
_coding style OK_
next parent reply other threads:[~2022-01-18 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <798beef100ce147f20e03f7590c7770e56a246cc.1642505511.git.jackmin@nvidia.com>
2022-01-18 11:40 ` checkpatch [this message]
2022-01-18 13:20 ` 0-day Robot
2022-01-18 17:31 dpdklab
2022-01-18 18:49 dpdklab
2022-01-18 19:04 dpdklab
2022-01-18 19:45 dpdklab
2022-01-18 19:51 dpdklab
2022-01-18 20:14 dpdklab
2022-01-18 20:29 dpdklab
2022-01-18 20:39 dpdklab
2022-01-18 20:41 dpdklab
2022-01-18 20:47 dpdklab
2022-01-18 22:07 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=20220118114046.0329D12091F@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).