From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136969 [PATCH] doc: deprecate graph data structures
Date: Wed, 21 Feb 2024 23:50:30 +0800 [thread overview]
Message-ID: <202402211550.41LFoUue3727972@localhost.localdomain> (raw)
In-Reply-To: <20240221161319.7054-1-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136969
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Wed, 21 Feb 2024 21:43:19 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 92d644f1d58838561d0996b2d4a9f5d276e41651
136969 --> 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-02-21 16:15 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240221161319.7054-1-pbhagavatula@marvell.com>
2024-02-21 15:50 ` qemudev [this message]
2024-02-21 15:54 ` qemudev
2024-02-21 16:14 ` checkpatch
2024-02-21 17:04 ` 0-day Robot
2024-02-23 19:46 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 5:59 dpdklab
2024-02-23 5:56 dpdklab
2024-02-23 5:54 dpdklab
2024-02-21 19:55 dpdklab
2024-02-21 19:03 dpdklab
2024-02-21 18:52 dpdklab
2024-02-21 18:45 dpdklab
2024-02-21 18:34 dpdklab
2024-02-21 18:32 dpdklab
2024-02-21 18:30 dpdklab
2024-02-21 18:29 dpdklab
2024-02-21 18:25 dpdklab
2024-02-21 18:21 dpdklab
2024-02-21 18:18 dpdklab
2024-02-21 18:10 dpdklab
2024-02-21 17:58 dpdklab
2024-02-21 17:52 dpdklab
2024-02-21 17:51 dpdklab
2024-02-21 17:50 dpdklab
2024-02-21 17:48 dpdklab
2024-02-21 17:47 dpdklab
2024-02-21 17:46 dpdklab
2024-02-21 17:45 dpdklab
2024-02-21 17:45 dpdklab
2024-02-21 17:43 dpdklab
2024-02-21 17:43 dpdklab
2024-02-21 17:43 dpdklab
2024-02-21 17:42 dpdklab
2024-02-21 17:41 dpdklab
2024-02-21 17:39 dpdklab
2024-02-21 17:38 dpdklab
2024-02-21 17:38 dpdklab
2024-02-21 17:38 dpdklab
2024-02-21 17:37 dpdklab
2024-02-21 17:37 dpdklab
2024-02-21 17:36 dpdklab
2024-02-21 17:34 dpdklab
2024-02-21 17:33 dpdklab
2024-02-21 17:20 dpdklab
2024-02-21 17:19 dpdklab
2024-02-21 17:19 dpdklab
2024-02-21 17:19 dpdklab
2024-02-21 17:19 dpdklab
2024-02-21 17:18 dpdklab
2024-02-21 17:18 dpdklab
2024-02-21 17:17 dpdklab
2024-02-21 17:14 dpdklab
2024-02-21 17:09 dpdklab
2024-02-21 17:08 dpdklab
2024-02-21 17:08 dpdklab
2024-02-21 17:08 dpdklab
2024-02-21 17:05 dpdklab
2024-02-21 17:03 dpdklab
2024-02-21 17:03 dpdklab
2024-02-21 17:02 dpdklab
2024-02-21 17:01 dpdklab
2024-02-21 17:01 dpdklab
2024-02-21 16:56 dpdklab
2024-02-21 16:55 dpdklab
2024-02-21 16:55 dpdklab
2024-02-21 16:52 dpdklab
2024-02-21 16:50 dpdklab
2024-02-21 16:49 dpdklab
2024-02-21 16:49 dpdklab
2024-02-21 16:49 dpdklab
2024-02-21 16:49 dpdklab
2024-02-21 16:48 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=202402211550.41LFoUue3727972@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).