automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "WanRenyong" <wanry@yunsilicon.com>
Subject: |WARNING| pw143933 [PATCH v2 19/19] net/xsc: add dev basic stats ops
Date: Wed, 11 Sep 2024 04:10:52 +0200 (CEST)	[thread overview]
Message-ID: <20240911021052.9B4B2121D10@dpdk.org> (raw)
In-Reply-To: <20240911020740.3950704-20-wanry@yunsilicon.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143933

_coding style issues_

Must be a reply to the first patch (--in-reply-to).

  parent reply	other threads:[~2024-09-11  2:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240911020740.3950704-20-wanry@yunsilicon.com>
2024-09-11  1:44 ` |FAILURE| pw143918-143933 " qemudev
2024-09-11  2:10 ` checkpatch [this message]
2024-09-11  2:56 ` |SUCCESS| pw143918-143933 [PATCH] [v2,19/19] net/xsc: add dev basic dpdklab
2024-09-11  3:00 ` dpdklab
2024-09-11  3:04 ` |FAILURE| pw143933 [PATCH v2 19/19] net/xsc: add dev basic stats ops 0-day Robot
2024-09-11  3:39 ` |SUCCESS| pw143918-143933 [PATCH] [v2,19/19] net/xsc: add dev basic dpdklab
2024-09-11  6:33 ` |PENDING| " dpdklab
2024-09-11  6:41 ` dpdklab
2024-09-11  6:49 ` |SUCCESS| " dpdklab
2024-09-11  6:49 ` dpdklab
2024-09-11  6:50 ` dpdklab
2024-09-11  7:08 ` |PENDING| " dpdklab
2024-09-11  8:33 ` |SUCCESS| " dpdklab
2024-09-11  9:48 ` dpdklab
2024-09-11 10:00 ` dpdklab
2024-09-11 11:16 ` |PENDING| " dpdklab
2024-09-11 15:38 ` |SUCCESS| " dpdklab
2024-09-11 15:42 ` dpdklab
2024-09-11 15:42 ` dpdklab
2024-09-11 15:46 ` dpdklab
2024-09-11 16:05 ` dpdklab
2024-09-11 16:09 ` dpdklab
2024-09-11 17:00 ` dpdklab
2024-09-11 17:46 ` dpdklab
2024-09-11 19:40 ` dpdklab
2024-09-15 19:58 ` dpdklab
2024-09-16  1:22 ` 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=20240911021052.9B4B2121D10@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=wanry@yunsilicon.com \
    /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).