automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anoob Joseph <anoobj@marvell.com>
Subject: |WARNING| pw139444 [PATCH v2 7/7] dma/odm: add remaining ops
Date: Wed, 17 Apr 2024 09:29:53 +0200 (CEST)	[thread overview]
Message-ID: <20240417072953.7D80D12083E@dpdk.org> (raw)
In-Reply-To: <20240417072708.322-8-anoobj@marvell.com>

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

_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

  parent reply	other threads:[~2024-04-17  7:29 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240417072708.322-8-anoobj@marvell.com>
2024-04-17  7:11 ` |SUCCESS| pw139438-139444 " qemudev
2024-04-17  7:15 ` qemudev
2024-04-17  7:29 ` checkpatch [this message]
2024-04-17  8:44 ` |FAILURE| pw139444 " 0-day Robot
2024-04-17  9:51 ` |SUCCESS| pw139438-139444 [PATCH] [v2,7/7] dma/odm: add remaining op dpdklab
2024-04-17  9:52 ` dpdklab
2024-04-17  9:53 ` dpdklab
2024-04-17  9:54 ` dpdklab
2024-04-17  9:55 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:15 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:16 ` dpdklab
2024-04-17 10:18 ` dpdklab
2024-04-17 10:18 ` dpdklab
2024-04-17 10:19 ` dpdklab
2024-04-17 10:19 ` dpdklab
2024-04-17 10:20 ` dpdklab
2024-04-17 10:20 ` dpdklab
2024-04-17 10:21 ` dpdklab
2024-04-17 10:23 ` dpdklab
2024-04-17 10:25 ` dpdklab
2024-04-17 10:26 ` dpdklab
2024-04-17 10:27 ` dpdklab
2024-04-17 10:27 ` dpdklab
2024-04-17 10:28 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:39 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:40 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:41 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:42 ` dpdklab
2024-04-17 10:43 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:44 ` dpdklab
2024-04-17 10:45 ` dpdklab
2024-04-17 10:45 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:46 ` dpdklab
2024-04-17 10:47 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:48 ` dpdklab
2024-04-17 10:51 ` dpdklab
2024-04-17 11:04 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:06 ` dpdklab
2024-04-17 11:08 ` dpdklab
2024-04-17 11:11 ` dpdklab
2024-04-17 11:12 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:16 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:19 ` dpdklab
2024-04-17 11:20 ` dpdklab
2024-04-17 11:24 ` dpdklab
2024-04-17 11:38 ` dpdklab
2024-04-17 11:38 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:39 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:40 ` dpdklab
2024-04-17 11:42 ` dpdklab
2024-04-17 11:43 ` dpdklab
2024-04-17 11:47 ` dpdklab
2024-04-17 11:49 ` dpdklab
2024-04-17 11:50 ` dpdklab
2024-04-17 11:54 ` dpdklab
2024-04-17 12:00 ` dpdklab
2024-04-17 12:11 ` dpdklab
2024-04-17 12:11 ` 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=20240417072953.7D80D12083E@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).