From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125053 [PATCH] net/e1000: fix saving of stripped VLAN TCI
Date: Sun, 12 Mar 2023 21:34:24 +0800 [thread overview]
Message-ID: <202303121334.32CDYOgg021354@localhost.localdomain> (raw)
In-Reply-To: <zrTH06r4LSoE18ww@hankala.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125053
_Compilation OK_
Submitter: Visa Hankala <visa@hankala.org>
Date: Sun, 12 Mar 2023 13:44:42 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: cb318a8ab1b07ebefe9a85ae52552ba3ddbf8e7b
125053 --> 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-03-12 13:48 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <zrTH06r4LSoE18ww@hankala.org>
2023-03-12 13:34 ` qemudev [this message]
2023-03-12 13:38 ` qemudev
2023-03-12 13:45 ` |WARNING| " checkpatch
2023-03-12 15:59 ` |SUCCESS| " 0-day Robot
2023-03-12 15:04 dpdklab
2023-03-12 15:09 dpdklab
2023-03-12 15:16 dpdklab
2023-03-12 15:16 dpdklab
2023-03-12 15:17 dpdklab
2023-03-12 15:18 dpdklab
2023-03-12 15:21 dpdklab
2023-03-12 15:22 dpdklab
2023-03-12 15:23 dpdklab
2023-03-12 15:26 dpdklab
2023-03-12 15:27 dpdklab
2023-03-12 15:31 dpdklab
2023-03-12 15:36 dpdklab
2023-03-12 16:03 dpdklab
2023-03-12 16:07 dpdklab
2023-03-12 16:08 dpdklab
2023-03-12 16:12 dpdklab
2023-03-12 16:18 dpdklab
2023-03-12 16:18 dpdklab
2023-03-12 16:20 dpdklab
2023-03-12 16:23 dpdklab
2023-03-12 16:24 dpdklab
2023-03-12 16:24 dpdklab
2023-03-12 16:28 dpdklab
2023-03-12 16:32 dpdklab
2023-03-12 16:37 dpdklab
2023-03-12 16:44 dpdklab
2023-03-12 17:13 dpdklab
2023-03-13 0:51 dpdklab
2023-03-13 0:58 dpdklab
2023-03-13 2:46 dpdklab
2023-03-13 4:03 dpdklab
2023-03-13 12:29 dpdklab
2023-03-13 12:38 dpdklab
2023-03-13 12:39 dpdklab
2023-03-13 12:42 dpdklab
2023-03-13 12:47 dpdklab
2023-03-13 12:49 dpdklab
2023-03-13 12:50 dpdklab
2023-03-13 12:57 dpdklab
2023-03-13 13:00 dpdklab
2023-03-13 13:10 dpdklab
2023-03-13 13:12 dpdklab
2023-03-13 14:11 dpdklab
2023-03-13 14:11 dpdklab
2023-03-13 15:16 dpdklab
2023-03-13 15:28 dpdklab
2023-03-13 15:34 dpdklab
2023-03-13 15:41 dpdklab
2023-03-13 15:42 dpdklab
2023-03-13 15:45 dpdklab
2023-03-13 15:50 dpdklab
2023-03-13 15:52 dpdklab
2023-03-13 15:54 dpdklab
2023-03-13 15:58 dpdklab
2023-03-13 16:03 dpdklab
2023-03-13 17:14 dpdklab
2023-03-13 17:14 dpdklab
2023-03-14 10:08 dpdklab
2023-03-14 11:30 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=202303121334.32CDYOgg021354@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).