From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Robin Zhang <robinx.zhang@intel.com>
Subject: |WARNING| pw109518 [PATCH v2] common/sff_module: add telemetry command to dump module EEPROM
Date: Fri, 8 Apr 2022 12:28:25 +0200 (CEST) [thread overview]
Message-ID: <20220408102825.3882B124163@dpdk.org> (raw)
In-Reply-To: <20220408102330.774749-1-robinx.zhang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/109518
_coding style issues_
ERROR:TRAILING_WHITESPACE: trailing whitespace
#866: FILE: drivers/common/sff_module/sff_8472.c:33:
+ * This is the offset at which the A2 page is in the EEPROM $
WARNING:TYPO_SPELLING: 'OTU' may be misspelled - perhaps 'OUT'?
#1592: FILE: drivers/common/sff_module/sff_8636.c:452:
+ printf("%s 40G OTN (OTU3B/OTU3C)
", pfx);
WARNING:TYPO_SPELLING: 'OTU' may be misspelled - perhaps 'OUT'?
#1592: FILE: drivers/common/sff_module/sff_8636.c:452:
+ printf("%s 40G OTN (OTU3B/OTU3C)
", pfx);
WARNING:TYPO_SPELLING: 'OTU' may be misspelled - perhaps 'OUT'?
#1593: FILE: drivers/common/sff_module/sff_8636.c:453:
+ add_item_string(items, name_string, "40G OTN (OTU3B/OTU3C)");
WARNING:TYPO_SPELLING: 'OTU' may be misspelled - perhaps 'OUT'?
#1593: FILE: drivers/common/sff_module/sff_8636.c:453:
+ add_item_string(items, name_string, "40G OTN (OTU3B/OTU3C)");
WARNING:TYPO_SPELLING: 'gurantee' may be misspelled - perhaps 'guarantee'?
#2022: FILE: drivers/common/sff_module/sff_8636.c:882:
+ * of page 3, will provide the gurantee for existence of alarms
WARNING:TYPO_SPELLING: 'Celcius' may be misspelled - perhaps ''?
#3336: FILE: drivers/common/sff_module/sff_common.h:167:
+ /* SFP Temp in 16-bit signed 1/256 Celcius */
ERROR:CODE_INDENT: code indent should use tabs where possible
#3534: FILE: drivers/common/sff_module/sff_telemetry.h:19:
+ char name[SFF_ITEM_NAME_SIZE]; /* The item name. */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#3534: FILE: drivers/common/sff_module/sff_telemetry.h:19:
+ char name[SFF_ITEM_NAME_SIZE]; /* The item name. */$
ERROR:CODE_INDENT: code indent should use tabs where possible
#3535: FILE: drivers/common/sff_module/sff_telemetry.h:20:
+ char value[SFF_ITEM_VALUE_SIZE]; /* The item value. */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#3535: FILE: drivers/common/sff_module/sff_telemetry.h:20:
+ char value[SFF_ITEM_VALUE_SIZE]; /* The item value. */$
total: 3 errors, 8 warnings, 3389 lines checked
next parent reply other threads:[~2022-04-08 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220408102330.774749-1-robinx.zhang@intel.com>
2022-04-08 10:28 ` checkpatch [this message]
2022-04-08 12:40 ` |FAILURE| " 0-day Robot
2022-04-09 2:22 |WARNING| pw109518 [PATCH] [v2] " dpdklab
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=20220408102825.3882B124163@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=robinx.zhang@intel.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).