From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147877 [PATCH v2] igc: fix invalid length and corrupted multi-segment mbufs
Date: Fri, 1 Nov 2024 21:27:09 +0800 [thread overview]
Message-ID: <202411011327.4A1DR9bI3711058@localhost.localdomain> (raw)
In-Reply-To: <00f78eba-8eff-4c67-8ecf-3bef5f25b9f6@allegro-packets.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147877
_Compilation OK_
Submitter: Martin Weiser <martin.weiser@allegro-packets.com>
Date: Fri, 1 Nov 2024 14:57:26 +0100
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 035326eb9633c344ee61e03fbcdf120a76c54830
147877 --> 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:[~2024-11-01 14:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00f78eba-8eff-4c67-8ecf-3bef5f25b9f6@allegro-packets.com>
2024-11-01 13:27 ` qemudev [this message]
2024-11-01 13:31 ` qemudev
2024-11-01 13:59 ` |WARNING| " checkpatch
2024-11-01 15:30 ` |SUCCESS| pw147877 [PATCH] [v2] igc: fix invalid length and corrupte dpdklab
2024-11-01 15:33 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:43 ` dpdklab
2024-11-01 15:48 ` dpdklab
2024-11-01 15:49 ` |PENDING| " dpdklab
2024-11-01 15:55 ` |SUCCESS| " dpdklab
2024-11-01 15:56 ` dpdklab
2024-11-01 16:32 ` |PENDING| " dpdklab
2024-11-01 16:35 ` dpdklab
2024-11-01 17:06 ` |SUCCESS| " dpdklab
2024-11-01 17:07 ` dpdklab
2024-11-01 18:26 ` |PENDING| " dpdklab
2024-11-01 18:57 ` |SUCCESS| " dpdklab
2024-11-01 22:11 ` dpdklab
2024-11-02 2:40 ` dpdklab
2024-11-02 18:04 ` dpdklab
2024-11-02 18:20 ` dpdklab
2024-11-02 18:56 ` dpdklab
2024-11-02 21:09 ` dpdklab
2024-11-03 2:31 ` dpdklab
2024-11-03 2:34 ` dpdklab
2024-11-06 6:57 ` 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=202411011327.4A1DR9bI3711058@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).