From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125796 [PATCH v2] eventdev/eth_rx: fix invalid memory access
Date: Wed, 5 Apr 2023 17:32:34 +0800 [thread overview]
Message-ID: <202304050932.3359WY4u3339625@localhost.localdomain> (raw)
In-Reply-To: <20230405094332.2862-1-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125796
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Wed, 5 Apr 2023 15:13:32 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 0a5f49fa6483e6178afe6ed7c9b9a723a904b812
125796 --> 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-04-05 9:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230405094332.2862-1-pbhagavatula@marvell.com>
2023-04-05 9:32 ` qemudev [this message]
2023-04-05 9:36 ` qemudev
2023-04-05 9:44 ` checkpatch
2023-04-05 10:38 ` 0-day Robot
2023-04-05 10:10 |SUCCESS| pw125796 [PATCH] [v2] " dpdklab
2023-04-05 10:14 dpdklab
2023-04-05 10:14 dpdklab
2023-04-05 10:17 dpdklab
2023-04-05 10:19 dpdklab
2023-04-05 10:19 dpdklab
2023-04-05 10:20 dpdklab
2023-04-05 10:21 dpdklab
2023-04-05 10:24 dpdklab
2023-04-05 10:25 dpdklab
2023-04-05 10:28 dpdklab
2023-04-05 10:33 dpdklab
2023-04-05 10:33 dpdklab
2023-04-05 10:37 dpdklab
2023-04-05 10:39 dpdklab
2023-04-05 10:40 dpdklab
2023-04-05 10:41 dpdklab
2023-04-05 10:42 dpdklab
2023-04-05 15:33 dpdklab
2023-04-06 0:36 dpdklab
2023-04-06 0:42 dpdklab
2023-04-06 0:44 dpdklab
2023-04-06 0:48 dpdklab
2023-04-06 0:51 dpdklab
2023-04-06 1:03 dpdklab
2023-04-06 1:03 dpdklab
2023-04-06 1:06 dpdklab
2023-04-06 1:10 dpdklab
2023-04-06 1:14 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=202304050932.3359WY4u3339625@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).