From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw92589 [kmods PATCH 3/3] windows/virt2phys: add tracing
Date: Sat, 1 May 2021 19:20:42 +0200 (CEST) [thread overview]
Message-ID: <20210501172042.EDE37121159@dpdk.org> (raw)
In-Reply-To: <20210501171837.13282-4-dmitry.kozliuk@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/92589
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#90:
[1]: https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/wpp-software-tracing
ERROR:SPACING: space required after that ',' (ctx:VxV)
#286: FILE: windows/virt2phys/virt2phys_trace.h:8:
+ VIRT2PHYS_TRACE_GUID, (C5C835BB,5CFB,4757,B1D4,9DD74662E212), \
^
ERROR:SPACING: space required after that ',' (ctx:VxV)
#286: FILE: windows/virt2phys/virt2phys_trace.h:8:
+ VIRT2PHYS_TRACE_GUID, (C5C835BB,5CFB,4757,B1D4,9DD74662E212), \
^
ERROR:SPACING: space required after that ',' (ctx:VxV)
#286: FILE: windows/virt2phys/virt2phys_trace.h:8:
+ VIRT2PHYS_TRACE_GUID, (C5C835BB,5CFB,4757,B1D4,9DD74662E212), \
^
ERROR:SPACING: space required after that ',' (ctx:VxV)
#286: FILE: windows/virt2phys/virt2phys_trace.h:8:
+ VIRT2PHYS_TRACE_GUID, (C5C835BB,5CFB,4757,B1D4,9DD74662E212), \
^
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#290: FILE: windows/virt2phys/virt2phys_trace.h:12:
+ WPP_LEVEL_LOGGER(flag)$
ERROR:SPACING: space required after that ',' (ctx:VxV)
#296: FILE: windows/virt2phys/virt2phys_trace.h:18:
+#define WPP_LEVEL_FLAGS_LOGGER(lvl,flags) \
^
WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#315: FILE: windows/virt2phys/virt2phys_trace.h:37:
+/*
+begin_wpp config
total: 5 errors, 3 warnings, 189 lines checked
parent reply other threads:[~2021-05-01 17:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210501171837.13282-4-dmitry.kozliuk@gmail.com>]
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=20210501172042.EDE37121159@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=dmitry.kozliuk@gmail.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).