automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137809 [PATCH] rte_memcpy: fix off by one for size 16 and 32
Date: Sun, 3 Mar 2024 04:27:20 +0800	[thread overview]
Message-ID: <202403022027.422KRKiv121082@localhost.localdomain> (raw)
In-Reply-To: <20240302204923.227105-1-stephen@networkplumber.org>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137809

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sat,  2 Mar 2024 12:49:23 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 5df34de5808a7b826b8bc035d6ee3161a12be364

137809 --> 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


       reply	other threads:[~2024-03-02 20:52 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240302204923.227105-1-stephen@networkplumber.org>
2024-03-02 20:27 ` qemudev [this message]
2024-03-02 20:31 ` qemudev
2024-03-02 20:51 ` checkpatch
2024-03-02 21:44 ` 0-day Robot
2024-03-02 21:48 ` |SUCCESS| pw137809 [PATCH] rte_memcpy: fix off by one for size 16 an dpdklab
2024-03-02 21:49 ` dpdklab
2024-03-02 21:49 ` dpdklab
2024-03-02 21:50 ` dpdklab
2024-03-02 21:50 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:52 ` dpdklab
2024-03-02 21:53 ` dpdklab
2024-03-02 21:54 ` dpdklab
2024-03-02 21:54 ` dpdklab
2024-03-02 21:55 ` dpdklab
2024-03-02 21:55 ` dpdklab
2024-03-02 21:57 ` dpdklab
2024-03-02 21:57 ` dpdklab
2024-03-02 21:59 ` dpdklab
2024-03-02 21:59 ` dpdklab
2024-03-02 21:59 ` dpdklab
2024-03-02 22:01 ` dpdklab
2024-03-02 22:01 ` dpdklab
2024-03-02 22:02 ` dpdklab
2024-03-02 22:02 ` dpdklab
2024-03-02 22:02 ` dpdklab
2024-03-02 22:03 ` dpdklab
2024-03-02 22:04 ` dpdklab
2024-03-02 22:04 ` dpdklab
2024-03-02 22:05 ` dpdklab
2024-03-02 22:05 ` dpdklab
2024-03-02 22:05 ` dpdklab
2024-03-02 22:06 ` dpdklab
2024-03-02 22:06 ` dpdklab
2024-03-02 22:06 ` dpdklab
2024-03-02 22:07 ` dpdklab
2024-03-02 22:07 ` dpdklab
2024-03-02 22:08 ` dpdklab
2024-03-02 22:08 ` dpdklab
2024-03-02 22:09 ` dpdklab
2024-03-02 22:09 ` dpdklab
2024-03-02 22:09 ` dpdklab
2024-03-02 22:12 ` dpdklab
2024-03-02 22:16 ` dpdklab
2024-03-02 22:17 ` dpdklab
2024-03-02 22:18 ` dpdklab
2024-03-02 22:18 ` dpdklab
2024-03-02 22:18 ` dpdklab
2024-03-02 22:19 ` dpdklab
2024-03-02 22:19 ` dpdklab
2024-03-02 22:20 ` dpdklab
2024-03-02 22:22 ` dpdklab
2024-03-02 22:24 ` dpdklab
2024-03-02 22:24 ` dpdklab
2024-03-02 22:24 ` dpdklab
2024-03-02 22:26 ` dpdklab
2024-03-02 22:28 ` dpdklab
2024-03-02 22:31 ` dpdklab
2024-03-02 22:32 ` dpdklab
2024-03-02 22:32 ` dpdklab
2024-03-02 22:34 ` dpdklab
2024-03-02 22:35 ` dpdklab
2024-03-02 22:42 ` dpdklab
2024-03-02 22:49 ` dpdklab
2024-03-02 23:11 ` dpdklab
2024-03-03  7:01 ` dpdklab
2024-03-06 17:41 ` dpdklab
2024-03-06 18:13 ` dpdklab
2024-03-06 18: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=202403022027.422KRKiv121082@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).