From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122772-122774 [PATCH 3/3] net/bnxt: do not corrupt RSS hash value in the mbuf
Date: Wed, 1 Feb 2023 12:17:09 +0800 [thread overview]
Message-ID: <202302010417.3114H9Lx1007149@localhost.localdomain> (raw)
In-Reply-To: <20230201042014.23526-4-kalesh-anakkur.purayil@broadcom.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122774
_Compilation OK_
Submitter: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Date: Wed, 1 Feb 2023 09:50:12 +0530
DPDK git baseline: Repo:dpdk-next-net-brcm
Branch: for-next-net
CommitID: d322a02bfaafd97e5970c26707db429555fdef7a
122772-122774 --> 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-01 4:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230201042014.23526-4-kalesh-anakkur.purayil@broadcom.com>
2023-02-01 4:17 ` qemudev [this message]
2023-02-01 4:21 ` qemudev
2023-02-01 4:23 ` |SUCCESS| pw122774 " checkpatch
2023-02-01 5:59 ` |SUCCESS| pw122774 [dpdk-dev] " 0-day Robot
2023-02-01 4:50 |SUCCESS| pw122772-122774 [PATCH] [3/3] " dpdklab
2023-02-01 4:51 dpdklab
2023-02-01 4:55 dpdklab
2023-02-01 4:56 dpdklab
2023-02-01 4:59 dpdklab
2023-02-01 5:06 dpdklab
2023-02-01 5:11 dpdklab
2023-02-01 6:31 dpdklab
2023-02-01 18:19 dpdklab
2023-02-01 18:20 dpdklab
2023-02-01 18:20 dpdklab
2023-02-01 18:20 dpdklab
2023-02-01 18:20 dpdklab
2023-02-01 18:20 dpdklab
2023-02-01 18:26 dpdklab
2023-02-01 18:27 dpdklab
2023-02-01 18:27 dpdklab
2023-02-02 4:50 dpdklab
2023-02-02 6:50 dpdklab
2023-02-02 8:45 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=202302010417.3114H9Lx1007149@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).