From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121743 [PATCH] sched: fix for tc_ov_enable flag position in subport structure.
Date: Mon, 9 Jan 2023 22:58:01 +0800 [thread overview]
Message-ID: <202301091458.309Ew1Yo1456782@localhost.localdomain> (raw)
In-Reply-To: <20230109145448.278463-1-megha.ajmera@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121743
_Compilation OK_
Submitter: Megha Ajmera <megha.ajmera@intel.com>
Date: Mon, 9 Jan 2023 14:54:48 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 373f4c7de8ff350548cacc3d56e788461677f2c7
121743 --> 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-09 15:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230109145448.278463-1-megha.ajmera@intel.com>
2023-01-09 14:58 ` qemudev [this message]
2023-01-09 14:59 ` checkpatch
2023-01-09 15:02 ` qemudev
2023-01-09 16:19 ` 0-day Robot
2023-01-10 1:23 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-10 0:41 dpdklab
2023-01-09 23:52 dpdklab
2023-01-09 19:34 dpdklab
2023-01-09 19:34 dpdklab
2023-01-09 19:33 dpdklab
2023-01-09 19:29 dpdklab
2023-01-09 19:29 dpdklab
2023-01-09 19:28 dpdklab
2023-01-09 19:28 dpdklab
2023-01-09 19:28 dpdklab
2023-01-09 19:27 dpdklab
2023-01-09 17:39 dpdklab
2023-01-09 15:51 dpdklab
2023-01-09 15:46 dpdklab
2023-01-09 15:44 dpdklab
2023-01-09 15:38 dpdklab
2023-01-09 15:37 dpdklab
2023-01-09 15:36 dpdklab
2023-01-09 15:31 dpdklab
2023-01-09 15: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=202301091458.309Ew1Yo1456782@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).