From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123208 [PATCH] doc: fix 22.11 release notes after acc200 driver rename
Date: Tue, 7 Feb 2023 16:14:22 +0800 [thread overview]
Message-ID: <202302070814.3178EMva190288@localhost.localdomain> (raw)
In-Reply-To: <20230207080524.1976354-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123208
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tue, 7 Feb 2023 09:05:23 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d3802886aaa76604833da59fa2df7cd519e59982
123208 --> 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 prev parent reply other threads:[~2023-02-07 8:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230207080524.1976354-1-david.marchand@redhat.com>
2023-02-07 8:07 ` |WARNING| " checkpatch
2023-02-07 8:14 ` qemudev [this message]
2023-02-07 8:18 ` |SUCCESS| " qemudev
2023-02-07 8:30 dpdklab
2023-02-07 8:37 dpdklab
2023-02-07 8:38 dpdklab
2023-02-07 8:44 dpdklab
2023-02-07 8:49 dpdklab
2023-02-07 8:54 dpdklab
2023-02-07 8:56 dpdklab
2023-02-07 9:01 dpdklab
2023-02-07 9:10 dpdklab
2023-02-07 9:13 dpdklab
2023-02-07 9:29 dpdklab
2023-02-07 12:15 dpdklab
2023-02-07 23:08 dpdklab
2023-02-08 0:19 dpdklab
2023-02-08 0:23 dpdklab
2023-02-08 0:43 dpdklab
2023-02-08 0:44 dpdklab
2023-02-08 0:44 dpdklab
2023-02-08 0:44 dpdklab
2023-02-08 0:44 dpdklab
2023-02-08 0:52 dpdklab
2023-02-08 0:52 dpdklab
2023-02-08 0:53 dpdklab
2023-02-08 9:23 dpdklab
2023-02-08 11:44 dpdklab
2023-02-08 18:15 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=202302070814.3178EMva190288@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).