automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Feifei Wang <wff_light@vip.163.com>
Subject: |WARNING| pw153021 [RFC 05/18] net/hinic3: add NIC event module
Date: Fri, 18 Apr 2025 11:13:04 +0200 (CEST)	[thread overview]
Message-ID: <20250418091304.9E807123FA7@dpdk.org> (raw)
In-Reply-To: <20250418090621.9638-6-wff_light@vip.163.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'alos' may be misspelled - perhaps 'also'?
#354: FILE: drivers/net/hinic3/base/hinic3_nic_event.c:273:
+		    "alos: %u, rx_los: %u, PCS 64 66b reg: 0x%x, "

WARNING:TYPO_SPELLING: 'alos' may be misspelled - perhaps 'also'?
#356: FILE: drivers/net/hinic3/base/hinic3_nic_event.c:275:
+		    port_info->alos, port_info->rx_los,

CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#510: FILE: drivers/net/hinic3/base/hinic3_nic_event.c:429:
+		    "Received nic ucode aeq event type: 0x%x, data: %" PRIu64,

total: 0 errors, 2 warnings, 1 checks, 472 lines checked

           reply	other threads:[~2025-04-18  9:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250418090621.9638-6-wff_light@vip.163.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=20250418091304.9E807123FA7@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=wff_light@vip.163.com \
    /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).