From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135931 [PATCH] doc: update LTS maintenance to 3 years
Date: Thu, 18 Jan 2024 00:07:56 +0800 [thread overview]
Message-ID: <202401171607.40HG7uvb2731023@localhost.localdomain> (raw)
In-Reply-To: <20240117161804.223582-1-ktraynor@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/135931
_Compilation OK_
Submitter: Kevin Traynor <ktraynor@redhat.com>
Date: Wed, 17 Jan 2024 16:18:04 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d4af9a82063e4c39568191eaa12955d3ca39581a
135931 --> 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:[~2024-01-17 16:32 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240117161804.223582-1-ktraynor@redhat.com>
2024-01-17 16:07 ` qemudev [this message]
2024-01-17 16:12 ` qemudev
2024-01-17 16:20 ` checkpatch
2024-01-17 17:14 ` 0-day Robot
2024-01-17 23:15 dpdklab
2024-01-17 23:29 dpdklab
2024-01-17 23:29 dpdklab
2024-01-17 23:30 dpdklab
2024-01-17 23:31 dpdklab
2024-01-17 23:31 dpdklab
2024-01-17 23:32 dpdklab
2024-01-17 23:32 dpdklab
2024-01-17 23:35 dpdklab
2024-01-17 23:36 dpdklab
2024-01-17 23:37 dpdklab
2024-01-17 23:38 dpdklab
2024-01-17 23:38 dpdklab
2024-01-17 23:47 dpdklab
2024-01-18 0:05 dpdklab
2024-01-18 0:05 dpdklab
2024-01-18 0:11 dpdklab
2024-01-18 0:13 dpdklab
2024-01-18 0:24 dpdklab
2024-01-18 0:36 dpdklab
2024-01-18 0:44 dpdklab
2024-01-18 0:46 dpdklab
2024-01-18 0:49 dpdklab
2024-01-18 0:56 dpdklab
2024-01-18 1:00 dpdklab
2024-01-18 1:00 dpdklab
2024-01-18 1:01 dpdklab
2024-01-18 1:02 dpdklab
2024-01-18 1:02 dpdklab
2024-01-18 1:03 dpdklab
2024-01-18 1:03 dpdklab
2024-01-18 1:05 dpdklab
2024-01-18 1:10 dpdklab
2024-01-18 1:10 dpdklab
2024-01-18 1:11 dpdklab
2024-01-18 1:11 dpdklab
2024-01-18 1:12 dpdklab
2024-01-18 1:12 dpdklab
2024-01-18 1:13 dpdklab
2024-01-18 1:13 dpdklab
2024-01-18 1:17 dpdklab
2024-01-18 1:18 dpdklab
2024-01-18 1:18 dpdklab
2024-01-18 1:19 dpdklab
2024-01-18 1:20 dpdklab
2024-01-18 1:22 dpdklab
2024-01-18 1:25 dpdklab
2024-01-18 1:30 dpdklab
2024-01-18 1:38 dpdklab
2024-01-18 1:40 dpdklab
2024-01-18 1:41 dpdklab
2024-01-18 1:41 dpdklab
2024-01-18 1:41 dpdklab
2024-01-18 1:43 dpdklab
2024-01-18 1:44 dpdklab
2024-01-18 1:44 dpdklab
2024-01-18 1:45 dpdklab
2024-01-18 1:46 dpdklab
2024-01-18 1:47 dpdklab
2024-01-18 1:48 dpdklab
2024-01-18 2:13 dpdklab
2024-01-18 2:13 dpdklab
2024-01-18 2:19 dpdklab
2024-01-18 2:20 dpdklab
2024-01-18 2:21 dpdklab
2024-01-18 2:32 dpdklab
2024-01-18 2:36 dpdklab
2024-01-18 2:44 dpdklab
2024-01-18 2:55 dpdklab
2024-01-18 7:52 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=202401171607.40HG7uvb2731023@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).