From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126677 [PATCH v2] build: announce requirement for C11
Date: Thu, 4 May 2023 01:22:28 +0800 [thread overview]
Message-ID: <202305031722.343HMSNp144520@localhost.localdomain> (raw)
In-Reply-To: <20230503173022.22160-1-bruce.richardson@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126677
_Compilation OK_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wed, 3 May 2023 18:30:22 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d03446724972d2a1bb645ce7f3e64f5ef0203d61
126677 --> 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-05-03 17:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230503173022.22160-1-bruce.richardson@intel.com>
2023-05-03 17:22 ` qemudev [this message]
2023-05-03 17:26 ` qemudev
2023-05-03 17:34 ` |WARNING| " checkpatch
2023-05-03 18:19 ` |SUCCESS| " 0-day Robot
2023-05-03 19:53 |SUCCESS| pw126677 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-05-03 19:14 dpdklab
2023-05-03 19:06 dpdklab
2023-05-03 18:50 dpdklab
2023-05-03 18:45 dpdklab
2023-05-03 18:43 dpdklab
2023-05-03 18:40 dpdklab
2023-05-03 18:39 dpdklab
2023-05-03 18:38 dpdklab
2023-05-03 18:38 dpdklab
2023-05-03 18:37 dpdklab
2023-05-03 18:36 dpdklab
2023-05-03 18:34 dpdklab
2023-05-03 18:34 dpdklab
2023-05-03 18:29 dpdklab
2023-05-03 18:29 dpdklab
2023-05-03 18:25 dpdklab
2023-05-03 18:21 dpdklab
2023-05-03 18:17 dpdklab
2023-05-03 18:16 dpdklab
2023-05-03 18:09 dpdklab
2023-05-03 18:09 dpdklab
2023-05-03 18:08 dpdklab
2023-05-03 18:04 dpdklab
2023-05-03 18:04 dpdklab
2023-05-03 18:03 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=202305031722.343HMSNp144520@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).