From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121529 [PATCH] net/mlx5: fix irrelevant send skew devarg warning
Date: Tue, 3 Jan 2023 19:09:23 +0800 [thread overview]
Message-ID: <202301031109.303B9NfB2243208@localhost.localdomain> (raw)
In-Reply-To: <20230103111113.29030-1-viacheslavo@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121529
_Compilation OK_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Tue, 3 Jan 2023 13:11:13 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: ea40920417296397f14236e46604d10a8c571706
121529 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2023-01-03 11:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230103111113.29030-1-viacheslavo@nvidia.com>
2023-01-03 11:09 ` qemudev [this message]
2023-01-03 11:13 ` checkpatch
2023-01-03 11:13 ` qemudev
2023-01-03 11:59 ` 0-day Robot
2023-01-03 18:06 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-03 17:13 dpdklab
2023-01-03 16:59 dpdklab
2023-01-03 16:59 dpdklab
2023-01-03 16:56 dpdklab
2023-01-03 16:56 dpdklab
2023-01-03 16:55 dpdklab
2023-01-03 16:55 dpdklab
2023-01-03 16:55 dpdklab
2023-01-03 16:42 dpdklab
2023-01-03 16:09 dpdklab
2023-01-03 14:45 dpdklab
2023-01-03 12:33 dpdklab
2023-01-03 12:26 dpdklab
2023-01-03 12:21 dpdklab
2023-01-03 12:05 dpdklab
2023-01-03 11:56 dpdklab
2023-01-03 11:51 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=202301031109.303B9NfB2243208@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).