From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw61779 [PATCH] event/octeontx2: use wfe while waiting for head
Date: Wed, 23 Oct 2019 18:13:59 +0200 (CEST) [thread overview]
Message-ID: <20191023161359.DE33E1C1DC@dpdk.org> (raw)
In-Reply-To: <20191023161244.3284-1-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/61779
_coding style issues_
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#46: FILE: drivers/event/octeontx2/otx2_worker.h:235:
+ " ldr %[tag], [%[tag_op]]
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#47: FILE: drivers/event/octeontx2/otx2_worker.h:236:
+ " tbnz %[tag], 35, done%=
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#48: FILE: drivers/event/octeontx2/otx2_worker.h:237:
+ " sevl
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#49: FILE: drivers/event/octeontx2/otx2_worker.h:238:
+ "rty%=: wfe
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#50: FILE: drivers/event/octeontx2/otx2_worker.h:239:
+ " ldr %[tag], [%[tag_op]]
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#51: FILE: drivers/event/octeontx2/otx2_worker.h:240:
+ " tbz %[tag], 35, rty%=
"
WARNING:QUOTED_WHITESPACE_BEFORE_NEWLINE: unnecessary whitespace before a quoted newline
#52: FILE: drivers/event/octeontx2/otx2_worker.h:241:
+ "done%=:
"
total: 0 errors, 7 warnings, 44 lines checked
next parent reply other threads:[~2019-10-23 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191023161244.3284-1-pbhagavatula@marvell.com>
2019-10-23 16:13 ` checkpatch [this message]
2019-10-24 9:03 ` [dpdk-test-report] |SUCCESS| pw61779 " 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=20191023161359.DE33E1C1DC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pbhagavatula@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).