automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138147 [PATCH 2/2] net/nfp: fix data endianness problem
Date: Mon, 11 Mar 2024 03:51:08 +0100 (CET)	[thread overview]
Message-ID: <20240311025108.D63201223EF@dpdk.org> (raw)
In-Reply-To: <20240311024939.2523778-3-chaoyong.he@corigine.com>

Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138147

_coding style OK_



  parent reply	other threads:[~2024-03-11  2:51 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240311024939.2523778-3-chaoyong.he@corigine.com>
2024-03-11  2:35 ` |SUCCESS| pw138146-138147 " qemudev
2024-03-11  2:39 ` qemudev
2024-03-11  2:51 ` checkpatch [this message]
2024-03-11  3:42 ` |SUCCESS| pw138147 " 0-day Robot
2024-03-11  7:11 ` |SUCCESS| pw138146-138147 [PATCH] [2/2] net/nfp: fix data endianness dpdklab
2024-03-11  7:15 ` dpdklab
2024-03-11  7:19 ` dpdklab
2024-03-11  7:25 ` dpdklab
2024-03-11  7:27 ` dpdklab
2024-03-11  7:29 ` dpdklab
2024-03-11  7:29 ` dpdklab
2024-03-11  7:29 ` dpdklab
2024-03-11  7:30 ` dpdklab
2024-03-11  7:31 ` dpdklab
2024-03-11  7:31 ` dpdklab
2024-03-11  7:31 ` dpdklab
2024-03-11  7:31 ` dpdklab
2024-03-11  7:32 ` dpdklab
2024-03-11  7:32 ` dpdklab
2024-03-11  7:33 ` dpdklab
2024-03-11  7:34 ` dpdklab
2024-03-11  7:34 ` dpdklab
2024-03-11  7:34 ` dpdklab
2024-03-11  7:45 ` dpdklab
2024-03-11  7:45 ` dpdklab
2024-03-11  7:45 ` dpdklab
2024-03-11  7:47 ` dpdklab
2024-03-11  7:47 ` dpdklab
2024-03-11  7:47 ` dpdklab
2024-03-11  7:47 ` dpdklab
2024-03-11  7:48 ` dpdklab
2024-03-11  7:48 ` dpdklab
2024-03-11  7:49 ` dpdklab
2024-03-11  7:49 ` dpdklab
2024-03-11  7:49 ` dpdklab
2024-03-11  7:49 ` dpdklab
2024-03-11  7:54 ` dpdklab
2024-03-11  8:01 ` dpdklab
2024-03-11  8:03 ` dpdklab
2024-03-11  8:04 ` dpdklab
2024-03-11  8:05 ` dpdklab
2024-03-11  8:06 ` dpdklab
2024-03-11  8:06 ` dpdklab
2024-03-11  8:06 ` dpdklab
2024-03-11  8:07 ` dpdklab
2024-03-11  8:07 ` dpdklab
2024-03-11  8:07 ` dpdklab
2024-03-11  8:08 ` dpdklab
2024-03-11  8:08 ` dpdklab
2024-03-11  8:09 ` dpdklab
2024-03-11  8:09 ` dpdklab
2024-03-11  8:11 ` dpdklab
2024-03-11  8:12 ` dpdklab
2024-03-11  8:13 ` dpdklab
2024-03-11  8:15 ` dpdklab
2024-03-11  8:17 ` dpdklab
2024-03-11  8:18 ` dpdklab
2024-03-11  8:18 ` dpdklab
2024-03-11  8:19 ` dpdklab
2024-03-11  8:20 ` dpdklab
2024-03-11  8:20 ` dpdklab
2024-03-11  8:22 ` dpdklab
2024-03-11  8:23 ` dpdklab
2024-03-11  8:24 ` dpdklab
2024-03-11  8:25 ` dpdklab
2024-03-11  8:25 ` dpdklab
2024-03-11  8:26 ` dpdklab
2024-03-11  8:27 ` dpdklab
2024-03-11  8:30 ` dpdklab
2024-03-11  8:32 ` dpdklab
2024-03-11  8:32 ` dpdklab
2024-03-11  8:33 ` dpdklab
2024-03-11  8:33 ` dpdklab
2024-03-11  8:46 ` dpdklab
2024-03-14 18:31 ` dpdklab
2024-03-14 18:49 ` 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=20240311025108.D63201223EF@dpdk.org \
    --to=checkpatch@dpdk.org \
    --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).