From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Howard Wang <howard_wang@realsil.com.cn>
Subject: |WARNING| pw140959 [PATCH v2] r8126: add r8126 ethernet poll mode driver
Date: Wed, 12 Jun 2024 13:34:01 +0200 (CEST) [thread overview]
Message-ID: <20240612113401.DCBA2124124@dpdk.org> (raw)
In-Reply-To: <20240612094032.5500-1-howard_wang@realsil.com.cn>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140959
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
next prev parent reply other threads:[~2024-06-12 11:34 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240612094032.5500-1-howard_wang@realsil.com.cn>
2024-06-12 11:17 ` |SUCCESS| " qemudev
2024-06-12 11:21 ` qemudev
2024-06-12 11:34 ` checkpatch [this message]
2024-06-12 12:24 ` |FAILURE| " 0-day Robot
2024-06-12 18:18 ` |SUCCESS| pw140959 [PATCH] [v2] r8126: add r8126 ethernet poll mode dpdklab
2024-06-12 18:19 ` dpdklab
2024-06-12 18:20 ` dpdklab
2024-06-12 18:23 ` dpdklab
2024-06-12 18:33 ` dpdklab
2024-06-12 18:54 ` dpdklab
2024-06-12 20:21 ` dpdklab
2024-06-12 20:22 ` dpdklab
2024-06-12 20:22 ` dpdklab
2024-06-12 20:32 ` dpdklab
2024-06-12 21:01 ` dpdklab
2024-06-12 21:25 ` dpdklab
2024-06-12 21:37 ` dpdklab
2024-06-12 21:40 ` dpdklab
2024-06-12 22:00 ` dpdklab
2024-06-12 22:32 ` dpdklab
2024-06-13 4:33 ` dpdklab
2024-06-13 4:33 ` dpdklab
2024-06-13 4:33 ` dpdklab
2024-06-13 4:34 ` dpdklab
2024-06-13 4:34 ` dpdklab
2024-06-13 4:35 ` dpdklab
2024-06-13 4:35 ` dpdklab
2024-06-13 4:35 ` dpdklab
2024-06-13 4:36 ` dpdklab
2024-06-13 4:36 ` dpdklab
2024-06-13 4:37 ` dpdklab
2024-06-13 4:37 ` dpdklab
2024-06-13 4:37 ` dpdklab
2024-06-13 4:38 ` dpdklab
2024-06-13 4:39 ` dpdklab
2024-06-13 4:40 ` dpdklab
2024-06-13 4:42 ` dpdklab
2024-06-13 4:42 ` dpdklab
2024-06-13 4:42 ` dpdklab
2024-06-13 4:42 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:43 ` dpdklab
2024-06-13 4:44 ` dpdklab
2024-06-13 4:44 ` dpdklab
2024-06-13 4:44 ` dpdklab
2024-06-13 4:44 ` dpdklab
2024-06-13 4:44 ` dpdklab
2024-06-13 4:44 ` dpdklab
2024-06-13 4:44 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:45 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:46 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:47 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:48 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:49 ` dpdklab
2024-06-13 4:50 ` dpdklab
2024-06-13 4:50 ` dpdklab
2024-06-13 4:50 ` dpdklab
2024-06-13 4:50 ` dpdklab
2024-06-13 4:50 ` dpdklab
2024-06-13 4:50 ` 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=20240612113401.DCBA2124124@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=howard_wang@realsil.com.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).