From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123362 [PATCH] app/dumpcap: don't pass negative value to strerror() on error
Date: Wed, 8 Feb 2023 00:51:59 +0800 [thread overview]
Message-ID: <202302071651.317Gpxgc1095843@localhost.localdomain> (raw)
In-Reply-To: <20230207170050.1093917-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123362
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 7 Feb 2023 09:00:50 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00
123362 --> 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-07 17:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230207170050.1093917-1-stephen@networkplumber.org>
2023-02-07 16:51 ` qemudev [this message]
2023-02-07 16:55 ` qemudev
2023-02-07 17:01 ` |SUCCESS| pw123362 [PATCH] app/dumpcap: don't pass negative value to strerror " checkpatch
2023-02-07 19:19 ` |SUCCESS| pw123362 [PATCH] app/dumpcap: don't pass negative value to strerror() " 0-day Robot
2023-02-07 17:34 dpdklab
2023-02-07 17:41 dpdklab
2023-02-07 17:56 dpdklab
2023-02-07 18:08 dpdklab
2023-02-07 18:20 dpdklab
2023-02-07 18:36 dpdklab
2023-02-07 18:47 dpdklab
2023-02-07 19:07 dpdklab
2023-02-07 19:59 dpdklab
2023-02-07 20:41 dpdklab
2023-02-07 20:52 dpdklab
2023-02-07 20:56 dpdklab
2023-02-08 17:02 dpdklab
2023-02-08 18:08 dpdklab
2023-02-08 18:09 dpdklab
2023-02-08 18:09 dpdklab
2023-02-08 18:10 dpdklab
2023-02-08 18:10 dpdklab
2023-02-08 18:10 dpdklab
2023-02-08 18:10 dpdklab
2023-02-08 18:10 dpdklab
2023-02-08 18:11 dpdklab
2023-02-09 6:13 dpdklab
2023-02-09 10:47 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=202302071651.317Gpxgc1095843@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).