From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yutang Jiang <jiangyutang@os.amperecomputing.com>
Subject: |WARNING| pw141963 [DPDK][PATCH v4] config/arm: add Ampere AmpereOneAC04 platform
Date: Fri, 28 Jun 2024 10:56:35 +0200 (CEST) [thread overview]
Message-ID: <20240628085635.12A6E128144@dpdk.org> (raw)
In-Reply-To: <20240628032247.10414-1-jiangyutang@os.amperecomputing.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/141963
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
next prev parent reply other threads:[~2024-06-28 8:57 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240628032247.10414-1-jiangyutang@os.amperecomputing.com>
2024-06-28 8:32 ` |SUCCESS| " qemudev
2024-06-28 8:36 ` qemudev
2024-06-28 8:56 ` checkpatch [this message]
2024-06-28 12:07 ` |SUCCESS| pw141963 [PATCH] [v4] config/arm: add Ampere AmpereOneAC04 dpdklab
2024-06-28 12:40 ` dpdklab
2024-06-28 12:43 ` dpdklab
2024-06-28 12:51 ` dpdklab
2024-06-28 12:53 ` dpdklab
2024-06-28 12:57 ` dpdklab
2024-06-28 13:04 ` dpdklab
2024-06-28 13:09 ` dpdklab
2024-06-28 13:23 ` dpdklab
2024-06-28 13:25 ` dpdklab
2024-06-28 13:27 ` dpdklab
2024-06-28 13:29 ` dpdklab
2024-06-28 13:29 ` dpdklab
2024-06-28 13:29 ` dpdklab
2024-06-28 13:34 ` dpdklab
2024-06-28 13:40 ` dpdklab
2024-06-28 13:55 ` dpdklab
2024-06-28 14:02 ` dpdklab
2024-06-28 14:05 ` |PENDING| " dpdklab
2024-06-28 14:05 ` dpdklab
2024-06-28 14:17 ` |SUCCESS| " dpdklab
2024-06-28 14:17 ` |PENDING| " dpdklab
2024-06-28 14:22 ` dpdklab
2024-06-28 14:23 ` dpdklab
2024-06-28 14:25 ` dpdklab
2024-06-28 14:34 ` dpdklab
2024-06-28 14:36 ` dpdklab
2024-06-28 14:37 ` |SUCCESS| " dpdklab
2024-06-28 14:43 ` |PENDING| " dpdklab
2024-06-28 14:46 ` dpdklab
2024-06-28 14:51 ` |SUCCESS| " dpdklab
2024-06-28 14:53 ` |PENDING| " dpdklab
2024-06-28 14:53 ` dpdklab
2024-06-28 14:55 ` |SUCCESS| " dpdklab
2024-06-28 14:56 ` |PENDING| " dpdklab
2024-06-28 14:57 ` dpdklab
2024-06-28 15:00 ` |SUCCESS| " dpdklab
2024-06-28 15:00 ` dpdklab
2024-06-28 15:05 ` dpdklab
2024-06-28 15:25 ` dpdklab
2024-06-28 16:45 ` dpdklab
2024-06-28 16:45 ` dpdklab
2024-06-28 16:45 ` dpdklab
2024-06-28 16:46 ` dpdklab
2024-06-28 16:46 ` dpdklab
2024-06-28 16:48 ` dpdklab
2024-06-28 16:50 ` dpdklab
2024-06-28 16:54 ` dpdklab
2024-06-28 16:54 ` dpdklab
2024-06-28 17:04 ` dpdklab
2024-06-28 17:04 ` dpdklab
2024-06-28 17:07 ` dpdklab
2024-06-28 17:07 ` dpdklab
2024-06-28 17:07 ` dpdklab
2024-06-28 17:08 ` dpdklab
2024-06-28 17:14 ` dpdklab
2024-06-28 17:15 ` dpdklab
2024-06-28 17:22 ` dpdklab
2024-06-28 23:03 ` |PENDING| " dpdklab
2024-06-28 23:12 ` dpdklab
2024-06-28 23:14 ` dpdklab
2024-06-28 23:16 ` dpdklab
2024-06-28 23:18 ` dpdklab
2024-06-28 23:19 ` dpdklab
2024-06-28 23:21 ` dpdklab
2024-06-28 23:21 ` dpdklab
2024-06-28 23:21 ` dpdklab
2024-06-28 23:22 ` dpdklab
2024-06-28 23:23 ` dpdklab
2024-06-28 23:25 ` dpdklab
2024-06-28 23:28 ` dpdklab
2024-06-28 23:28 ` dpdklab
2024-06-28 23:30 ` dpdklab
2024-06-28 23:31 ` dpdklab
2024-06-28 23:33 ` dpdklab
2024-06-28 23:35 ` dpdklab
2024-06-28 23:36 ` dpdklab
2024-06-28 23:40 ` dpdklab
2024-06-28 23:41 ` dpdklab
2024-06-28 23:42 ` dpdklab
2024-06-28 23:42 ` |SUCCESS| " dpdklab
2024-06-28 23:46 ` |PENDING| " dpdklab
2024-06-28 23:48 ` dpdklab
2024-06-28 23:48 ` dpdklab
2024-06-28 23:49 ` dpdklab
2024-06-28 23:49 ` dpdklab
2024-06-28 23:51 ` dpdklab
2024-06-28 23:51 ` dpdklab
2024-06-28 23:52 ` dpdklab
2024-06-28 23:54 ` dpdklab
2024-06-28 23:59 ` dpdklab
2024-06-29 0:07 ` |SUCCESS| " dpdklab
2024-06-29 0:31 ` |PENDING| " dpdklab
2024-06-29 0:46 ` |SUCCESS| " dpdklab
2024-06-29 0:55 ` |PENDING| " dpdklab
2024-06-29 0:58 ` |SUCCESS| " dpdklab
2024-06-29 1:00 ` dpdklab
2024-06-29 11:00 ` 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=20240628085635.12A6E128144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jiangyutang@os.amperecomputing.com \
--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).