From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124716 [PATCH] net/ice: fix incorrect Rx timestamp for E822
Date: Mon, 6 Mar 2023 15:18:37 +0800 [thread overview]
Message-ID: <202303060718.3267Ib1a3957872@localhost.localdomain> (raw)
In-Reply-To: <20230302134501.201032-1-simei.su@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124716
_Compilation OK_
Submitter: Simei Su <simei.su@intel.com>
Date: Thu, 2 Mar 2023 21:45:01 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 5394c0f209b056e3ee9c8ea97939236ebdcb7c85
124716 --> 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-03-06 7:32 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302134501.201032-1-simei.su@intel.com>
2023-03-02 13:46 ` checkpatch
2023-03-02 15:59 ` 0-day Robot
2023-03-06 7:18 ` qemudev [this message]
2023-03-06 7:19 ` qemudev
2023-03-03 20:13 dpdklab
2023-03-03 20:15 dpdklab
2023-03-03 20:20 dpdklab
2023-03-03 20:23 dpdklab
2023-03-03 20:26 dpdklab
2023-03-03 20:27 dpdklab
2023-03-03 20:30 dpdklab
2023-03-03 20:31 dpdklab
2023-03-03 20:32 dpdklab
2023-03-03 20:34 dpdklab
2023-03-03 20:42 dpdklab
2023-03-03 20:44 dpdklab
2023-03-03 20:55 dpdklab
2023-03-03 20:55 dpdklab
2023-03-03 21:01 dpdklab
2023-03-03 21:04 dpdklab
2023-03-03 21:06 dpdklab
2023-03-03 21:08 dpdklab
2023-03-03 21:13 dpdklab
2023-03-03 21:14 dpdklab
2023-03-03 21:15 dpdklab
2023-03-03 21:17 dpdklab
2023-03-03 21:21 dpdklab
2023-03-03 21:27 dpdklab
2023-03-03 21:56 dpdklab
2023-03-04 3:36 dpdklab
2023-03-04 6:32 dpdklab
2023-03-04 11:28 dpdklab
2023-03-04 12:31 dpdklab
2023-03-04 13:56 dpdklab
2023-03-04 14:57 dpdklab
2023-03-05 10:38 dpdklab
2023-03-05 10:39 dpdklab
2023-03-05 10:48 dpdklab
2023-03-05 10:49 dpdklab
2023-03-05 10:52 dpdklab
2023-03-05 10:53 dpdklab
2023-03-05 10:54 dpdklab
2023-03-05 10:57 dpdklab
2023-03-05 10:58 dpdklab
2023-03-05 11:00 dpdklab
2023-03-05 11:01 dpdklab
2023-03-05 11:02 dpdklab
2023-03-05 11:05 dpdklab
2023-03-05 11:05 dpdklab
2023-03-05 11:30 dpdklab
2023-03-05 11:34 dpdklab
2023-03-05 11:39 dpdklab
2023-03-05 11:41 dpdklab
2023-03-05 11:42 dpdklab
2023-03-05 11:42 dpdklab
2023-03-05 11:44 dpdklab
2023-03-05 11:45 dpdklab
2023-03-05 11:47 dpdklab
2023-03-05 11:50 dpdklab
2023-03-05 11:51 dpdklab
2023-03-05 11:55 dpdklab
2023-03-05 11:57 dpdklab
2023-03-05 11:57 dpdklab
2023-03-06 2:36 dpdklab
2023-03-06 2:39 dpdklab
2023-03-06 2:44 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=202303060718.3267Ib1a3957872@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).