From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anoob Joseph <anoobj@marvell.com>
Subject: |WARNING| pw139290 [PATCH 8/8] dma/odm: add remaining ops
Date: Mon, 15 Apr 2024 17:33:53 +0200 (CEST) [thread overview]
Message-ID: <20240415153353.11EC912083E@dpdk.org> (raw)
In-Reply-To: <20240415153159.86-9-anoobj@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139290
_coding style issues_
ERROR:SPACING: space prohibited before that close parenthesis ')'
#225: FILE: drivers/dma/odm/odm.h:80:
+ RTE_FMT("%s(): %u" RTE_FMT_HEAD(__VA_ARGS__, ), __func__, __LINE__, \
ERROR:SPACING: space prohibited before that close parenthesis ')'
#226: FILE: drivers/dma/odm/odm.h:81:
+ RTE_FMT_TAIL(__VA_ARGS__, )))
total: 2 errors, 0 warnings, 371 lines checked
next prev parent reply other threads:[~2024-04-15 15:33 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240415153159.86-9-anoobj@marvell.com>
2024-04-15 15:09 ` |SUCCESS| pw139283-139290 " qemudev
2024-04-15 15:14 ` qemudev
2024-04-15 15:33 ` checkpatch [this message]
2024-04-15 16:24 ` |FAILURE| pw139290 " 0-day Robot
2024-04-15 18:05 ` |SUCCESS| pw139283-139290 [PATCH] [8/8] " dpdklab
2024-04-15 18:07 ` dpdklab
2024-04-15 18:07 ` dpdklab
2024-04-15 18:08 ` dpdklab
2024-04-15 18:09 ` dpdklab
2024-04-15 18:32 ` dpdklab
2024-04-15 18:32 ` dpdklab
2024-04-15 18:33 ` dpdklab
2024-04-15 18:34 ` dpdklab
2024-04-15 18:34 ` dpdklab
2024-04-15 18:35 ` dpdklab
2024-04-15 18:35 ` dpdklab
2024-04-15 18:35 ` |FAILURE| " dpdklab
2024-04-15 18:35 ` |SUCCESS| " dpdklab
2024-04-15 18:36 ` dpdklab
2024-04-15 18:36 ` |FAILURE| " dpdklab
2024-04-15 18:36 ` dpdklab
2024-04-15 18:36 ` |SUCCESS| " dpdklab
2024-04-15 18:36 ` |FAILURE| " dpdklab
2024-04-15 18:37 ` |SUCCESS| " dpdklab
2024-04-15 18:37 ` |FAILURE| " dpdklab
2024-04-15 18:37 ` dpdklab
2024-04-15 18:37 ` |SUCCESS| " dpdklab
2024-04-15 18:37 ` dpdklab
2024-04-15 18:37 ` |FAILURE| " dpdklab
2024-04-15 18:38 ` |SUCCESS| " dpdklab
2024-04-15 18:38 ` |FAILURE| " dpdklab
2024-04-15 18:38 ` |SUCCESS| " dpdklab
2024-04-15 18:38 ` |FAILURE| " dpdklab
2024-04-15 18:39 ` dpdklab
2024-04-15 18:39 ` dpdklab
2024-04-15 18:39 ` |SUCCESS| " dpdklab
2024-04-15 18:39 ` |FAILURE| " dpdklab
2024-04-15 18:39 ` |SUCCESS| " dpdklab
2024-04-15 18:39 ` |FAILURE| " dpdklab
2024-04-15 18:39 ` |SUCCESS| " dpdklab
2024-04-15 18:39 ` dpdklab
2024-04-15 18:39 ` dpdklab
2024-04-15 18:40 ` dpdklab
2024-04-15 18:40 ` |FAILURE| " dpdklab
2024-04-15 18:40 ` |SUCCESS| " dpdklab
2024-04-15 18:40 ` |FAILURE| " dpdklab
2024-04-15 18:40 ` dpdklab
2024-04-15 18:40 ` dpdklab
2024-04-15 18:40 ` dpdklab
2024-04-15 18:41 ` |SUCCESS| " dpdklab
2024-04-15 18:41 ` |FAILURE| " dpdklab
2024-04-15 18:41 ` |SUCCESS| " dpdklab
2024-04-15 18:41 ` dpdklab
2024-04-15 18:41 ` |FAILURE| " dpdklab
2024-04-15 18:42 ` |SUCCESS| " dpdklab
2024-04-15 18:42 ` |FAILURE| " dpdklab
2024-04-15 18:42 ` dpdklab
2024-04-15 18:42 ` dpdklab
2024-04-15 18:42 ` dpdklab
2024-04-15 18:43 ` dpdklab
2024-04-15 18:43 ` dpdklab
2024-04-15 18:44 ` |SUCCESS| " dpdklab
2024-04-15 18:44 ` dpdklab
2024-04-15 18:45 ` dpdklab
2024-04-15 18:46 ` |FAILURE| " dpdklab
2024-04-15 18:46 ` |SUCCESS| " dpdklab
2024-04-15 18:48 ` |FAILURE| " dpdklab
2024-04-15 18:49 ` |SUCCESS| " dpdklab
2024-04-15 18:50 ` dpdklab
2024-04-15 18:50 ` dpdklab
2024-04-15 18:51 ` dpdklab
2024-04-15 18:51 ` dpdklab
2024-04-15 18:52 ` |FAILURE| " dpdklab
2024-04-15 18:52 ` dpdklab
2024-04-15 18:52 ` dpdklab
2024-04-15 18:54 ` dpdklab
2024-04-15 18:56 ` dpdklab
2024-04-15 18:58 ` |SUCCESS| " dpdklab
2024-04-15 19:00 ` dpdklab
2024-04-15 19:01 ` dpdklab
2024-04-15 19:03 ` dpdklab
2024-04-15 19:06 ` dpdklab
2024-04-15 19:11 ` dpdklab
2024-04-15 19:15 ` dpdklab
2024-04-15 19:16 ` dpdklab
2024-04-15 19:39 ` dpdklab
2024-04-15 19:42 ` dpdklab
2024-04-15 19:45 ` dpdklab
2024-04-15 19:50 ` dpdklab
2024-04-15 19:53 ` 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=20240415153353.11EC912083E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anoobj@marvell.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).