From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw135262 [PATCH v3 14/14] lib: use per line logging in helpers
Date: Mon, 18 Dec 2023 10:31:53 +0100 (CET) [thread overview]
Message-ID: <20231218093153.2A7D6121E47@dpdk.org> (raw)
In-Reply-To: <20231218092738.749604-15-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/135262
_coding style issues_
ERROR:SPACING: space required after that ',' (ctx:VxB)
#214: FILE: lib/cryptodev/rte_cryptodev.h:40:
+ RTE_FMT("%s() line %u: " RTE_FMT_HEAD(__VA_ARGS__,), \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#227: FILE: lib/cryptodev/rte_cryptodev.h:48:
+ RTE_FMT("%s() line %u: " RTE_FMT_HEAD(__VA_ARGS__,), \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#234: FILE: lib/cryptodev/rte_cryptodev.h:53:
+ RTE_FMT("[%s] %s: " RTE_FMT_HEAD(__VA_ARGS__,), \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#251: FILE: lib/dmadev/rte_dmadev.c:38:
+ RTE_LOG_LINE(level, DMA, RTE_FMT("dma: " RTE_FMT_HEAD(__VA_ARGS__,), \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#252: FILE: lib/dmadev/rte_dmadev.c:39:
+ RTE_FMT_TAIL(__VA_ARGS__,)))
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#281: FILE: lib/eventdev/eventdev_pmd.h:37:
+ RTE_FMT("%s() line %u: " RTE_FMT_HEAD(__VA_ARGS__,), \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#289: FILE: lib/eventdev/eventdev_pmd.h:43:
+ RTE_FMT("%s() line %u: " RTE_FMT_HEAD(__VA_ARGS__,), \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#316: FILE: lib/eventdev/rte_event_timer_adapter.c:45:
+ RTE_FMT("EVTIMER: %s() line %u: " RTE_FMT_HEAD(__VA_ARGS__,), \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#317: FILE: lib/eventdev/rte_event_timer_adapter.c:46:
+ __func__, __LINE__, RTE_FMT_TAIL(__VA_ARGS__,)))
^
ERROR:SPACING: space prohibited before that close parenthesis ')'
#348: FILE: lib/gpudev/gpudev.c:23:
+ RTE_LOG_LINE(level, GPUDEV, RTE_FMT("gpu: " RTE_FMT_HEAD(__VA_ARGS__, ), \
ERROR:SPACING: space prohibited before that close parenthesis ')'
#349: FILE: lib/gpudev/gpudev.c:24:
+ RTE_FMT_TAIL(__VA_ARGS__, )))
ERROR:SPACING: space prohibited before that close parenthesis ')'
#367: FILE: lib/graph/graph_private.h:25:
+ RTE_FMT("GRAPH: %s():%u " RTE_FMT_HEAD(__VA_ARGS__, ), \
ERROR:SPACING: space required after that ',' (ctx:VxB)
#382: FILE: lib/member/member.h:12:
+ RTE_FMT("%s(): " RTE_FMT_HEAD(__VA_ARGS__,), \
^
ERROR:SPACING: space prohibited before that close parenthesis ')'
#454: FILE: lib/node/node_private.h:18:
+ RTE_FMT("NODE %s: %s():%u " RTE_FMT_HEAD(__VA_ARGS__, ), \
total: 14 errors, 0 warnings, 357 lines checked
next prev parent reply other threads:[~2023-12-18 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231218092738.749604-15-david.marchand@redhat.com>
2023-12-18 9:17 ` |SUCCESS| pw135250-135262 " qemudev
2023-12-18 9:22 ` qemudev
2023-12-18 9:31 ` checkpatch [this message]
2023-12-18 10:23 ` |SUCCESS| pw135262 " 0-day Robot
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=20231218093153.2A7D6121E47@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=david.marchand@redhat.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).