From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124187 [PATCH] doc: fix reference to event timer header
Date: Mon, 20 Feb 2023 22:35:47 +0800 [thread overview]
Message-ID: <202302201435.31KEZl293588791@localhost.localdomain> (raw)
In-Reply-To: <20230220144711.2698257-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124187
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Mon, 20 Feb 2023 15:47:11 +0100
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 44fe1187305af8ac6d31c46113c1ca35405de77b
124187 --> 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-02-20 14:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230220144711.2698257-1-david.marchand@redhat.com>
2023-02-20 14:35 ` qemudev [this message]
2023-02-20 14:39 ` qemudev
2023-02-20 14:47 ` checkpatch
2023-02-20 16:59 ` 0-day Robot
2023-02-20 15:07 dpdklab
2023-02-20 15:11 dpdklab
2023-02-20 15:16 dpdklab
2023-02-20 15:16 dpdklab
2023-02-20 15:17 dpdklab
2023-02-20 15:20 dpdklab
2023-02-20 15:22 dpdklab
2023-02-20 15:24 dpdklab
2023-02-20 15:32 dpdklab
2023-02-20 15:37 dpdklab
2023-02-20 15:58 dpdklab
2023-02-20 16:38 dpdklab
2023-02-20 16:40 dpdklab
2023-02-20 16:43 dpdklab
2023-02-20 16:45 dpdklab
2023-02-20 16:48 dpdklab
2023-02-20 16:49 dpdklab
2023-02-20 16:51 dpdklab
2023-02-20 16:52 dpdklab
2023-02-20 16:54 dpdklab
2023-02-20 16:55 dpdklab
2023-02-20 16:56 dpdklab
2023-02-20 18:45 dpdklab
2023-02-21 14:34 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=202302201435.31KEZl293588791@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).