automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shijith Thotton <sthotton@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw94776 [PATCH v2 2/2] drivers: add octeontx crypto adapter data path
Date: Wed, 23 Jun 2021 22:55:04 +0200 (CEST)	[thread overview]
Message-ID: <20210623205504.7A73F122E3A@dpdk.org> (raw)
In-Reply-To: <0686a7c3fb3a22e37378a8545bc37bce04f4c391.1624481225.git.sthotton@marvell.com>

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

_coding style issues_


ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#174: FILE: drivers/crypto/octeontx/otx_cryptodev_ops.c:419:
+static __rte_always_inline void * __rte_hot

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#207: FILE: drivers/crypto/octeontx/otx_cryptodev_ops.c:448:
+static __rte_always_inline void * __rte_hot

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#256: FILE: drivers/crypto/octeontx/otx_cryptodev_ops.c:530:
+static __rte_always_inline void * __rte_hot

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#293: FILE: drivers/crypto/octeontx/otx_cryptodev_ops.c:572:
+static __rte_always_inline void * __rte_hot

total: 4 errors, 0 warnings, 596 lines checked
--- a/doc/guides/rel_notes/release_21_08.rst
+++ b/doc/guides/rel_notes/release_21_08.rst

       reply	other threads:[~2021-06-23 20:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0686a7c3fb3a22e37378a8545bc37bce04f4c391.1624481225.git.sthotton@marvell.com>
2021-06-23 20:55 ` checkpatch [this message]
2021-06-23 22:02 ` [dpdk-test-report] |SUCCESS| pw94776 [dpdk-dev] " 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=20210623205504.7A73F122E3A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=sthotton@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).