automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [dpdk-test-report] |WARNING| pw95196 [PATCH v4 13/20] common/sfc_efx/base: add counter creation MCDI wrappers
Date: Fri,  2 Jul 2021 10:43:09 +0200 (CEST)	[thread overview]
Message-ID: <20210702084309.56367122E89@dpdk.org> (raw)
In-Reply-To: <20210702083948.546667-14-andrew.rybchenko@oktetlabs.ru>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'allocatedp' may be misspelled - perhaps 'allocated'?
#117: FILE: drivers/common/sfc_efx/base/efx.h:4427:
+	__out				uint32_t *n_allocatedp,

ERROR:RETURN_PARENTHESES: return is not a function, parentheses are not required
#171: FILE: drivers/common/sfc_efx/base/efx_mae.c:2383:
+	return (rc);

WARNING:TYPO_SPELLING: 'allocatedp' may be misspelled - perhaps 'allocated'?
#178: FILE: drivers/common/sfc_efx/base/efx_mae.c:2390:
+	__out				uint32_t *n_allocatedp,

WARNING:TYPO_SPELLING: 'allocatedp' may be misspelled - perhaps 'allocated'?
#236: FILE: drivers/common/sfc_efx/base/efx_mae.c:2448:
+	*n_allocatedp = n_allocated;

ERROR:RETURN_PARENTHESES: return is not a function, parentheses are not required
#238: FILE: drivers/common/sfc_efx/base/efx_mae.c:2450:
+	return (0);

ERROR:RETURN_PARENTHESES: return is not a function, parentheses are not required
#249: FILE: drivers/common/sfc_efx/base/efx_mae.c:2461:
+	return (rc);

ERROR:RETURN_PARENTHESES: return is not a function, parentheses are not required
#316: FILE: drivers/common/sfc_efx/base/efx_mae.c:2528:
+	return (0);

total: 4 errors, 3 warnings, 253 lines checked

           reply	other threads:[~2021-07-02  8:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210702083948.546667-14-andrew.rybchenko@oktetlabs.ru>]

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=20210702084309.56367122E89@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --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).