From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129258 [PATCH] pcap: support MTU set
Date: Wed, 5 Jul 2023 01:32:28 +0800 [thread overview]
Message-ID: <202307041732.364HWSwo914373@localhost.localdomain> (raw)
In-Reply-To: <20230704174357.68674-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129258
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 4 Jul 2023 10:43:57 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 832c574469dbc7062aa91405eb3f2d465a1ec81e
129258 --> 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-07-04 17:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230704174357.68674-1-stephen@networkplumber.org>
2023-07-04 17:32 ` qemudev [this message]
2023-07-04 17:36 ` qemudev
2023-07-04 17:45 ` checkpatch
2023-07-04 18:39 ` 0-day Robot
2023-07-05 22:40 dpdklab
2023-07-05 22:41 dpdklab
2023-07-05 22:50 dpdklab
2023-07-05 23:30 dpdklab
2023-07-05 23:30 dpdklab
2023-07-05 23:31 dpdklab
2023-07-05 23:31 dpdklab
2023-07-05 23:32 dpdklab
2023-07-05 23:32 dpdklab
2023-07-05 23:32 dpdklab
2023-07-05 23:32 dpdklab
2023-07-05 23:33 dpdklab
2023-07-05 23:35 dpdklab
2023-07-05 23:37 dpdklab
2023-07-06 2:16 dpdklab
2023-07-06 2:25 dpdklab
2023-07-06 3:14 dpdklab
2023-07-07 15:19 dpdklab
2023-07-07 15:42 dpdklab
2023-07-10 13:59 dpdklab
2023-07-11 3:36 dpdklab
2023-07-11 14:59 dpdklab
2023-07-11 20:23 dpdklab
2023-07-11 21:08 dpdklab
2023-07-11 21:08 dpdklab
2023-07-11 21:14 dpdklab
2023-07-11 21:19 dpdklab
2023-07-11 21:56 dpdklab
2023-07-11 23:29 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=202307041732.364HWSwo914373@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).