From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122179 [RFC] Fix cryptodev socket id for devices on unknown NUMA node
Date: Tue, 17 Jan 2023 18:09:21 +0800 [thread overview]
Message-ID: <202301171009.30HA9LmU1539028@localhost.localdomain> (raw)
In-Reply-To: <20230117101646.2521875-1-didier.pallard@6wind.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122179
_Compilation OK_
Submitter: Didier Pallard <didier.pallard@6wind.com>
Date: Tue, 17 Jan 2023 11:16:46 +0100
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 2a77219943174c2a4ed4da0366636a4e84976167
122179 --> 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-01-17 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230117101646.2521875-1-didier.pallard@6wind.com>
2023-01-17 10:09 ` qemudev [this message]
2023-01-17 10:13 ` qemudev
2023-01-17 10:17 ` |WARNING| " checkpatch
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=202301171009.30HA9LmU1539028@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).