From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124404 [PATCH v2] net/bnxt: remove compile-time option for IEEE 1588
Date: Thu, 23 Feb 2023 02:12:33 +0800 [thread overview]
Message-ID: <202302221812.31MICXTa2210825@localhost.localdomain> (raw)
In-Reply-To: <20230222182244.19294-1-ajit.khaparde@broadcom.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124404
_Compilation OK_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Wed, 22 Feb 2023 10:22:44 -0800
DPDK git baseline: Repo:dpdk-next-net-brcm
Branch: for-next-net
CommitID: c0ada8f28ae3385f76dea53e601ddf9d953f392a
124404 --> 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-22 18:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230222182244.19294-1-ajit.khaparde@broadcom.com>
2023-02-22 18:12 ` qemudev [this message]
2023-02-22 18:16 ` qemudev
2023-02-22 18:23 ` |WARNING| " checkpatch
2023-02-22 20:59 ` |SUCCESS| " 0-day Robot
2023-02-24 11:38 |SUCCESS| pw124404 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 3:09 dpdklab
2023-02-22 22:17 dpdklab
2023-02-22 22:17 dpdklab
2023-02-22 22:14 dpdklab
2023-02-22 22:13 dpdklab
2023-02-22 22:09 dpdklab
2023-02-22 22:04 dpdklab
2023-02-22 22:03 dpdklab
2023-02-22 22:02 dpdklab
2023-02-22 22:01 dpdklab
2023-02-22 21:58 dpdklab
2023-02-22 21:50 dpdklab
2023-02-22 21:49 dpdklab
2023-02-22 21:48 dpdklab
2023-02-22 19:12 dpdklab
2023-02-22 19:08 dpdklab
2023-02-22 19:06 dpdklab
2023-02-22 19:05 dpdklab
2023-02-22 19:05 dpdklab
2023-02-22 19:02 dpdklab
2023-02-22 18:59 dpdklab
2023-02-22 18:54 dpdklab
2023-02-22 18:52 dpdklab
2023-02-22 18: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=202302221812.31MICXTa2210825@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).