automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ivan Malov <ivan.malov@arknetworks.am>
Subject: |WARNING| pw153111 [PATCH v2 28/45] common/sfc_efx/base: provide PHY link get method on Medford4
Date: Wed, 23 Apr 2025 18:07:19 +0200 (CEST)	[thread overview]
Message-ID: <20250423160719.3F0421251C3@dpdk.org> (raw)
In-Reply-To: <20250423160002.35706-29-ivan.malov@arknetworks.am>

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

_coding style issues_


WARNING:SPACING: space prohibited between function name and open parenthesis '('
#278: FILE: drivers/common/sfc_efx/base/efx_np.c:634:
+	memset(msp, 0, sizeof (*msp));

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

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

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

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

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

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

total: 6 errors, 1 warnings, 280 lines checked

           reply	other threads:[~2025-04-23 16:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250423160002.35706-29-ivan.malov@arknetworks.am>]

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=20250423160719.3F0421251C3@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=ivan.malov@arknetworks.am \
    --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).