From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>
Subject: [dpdk-test-report] |WARNING| pw35241 [PATCH 02/80] net/sfc/base: regenerate files with genfwdef after ID update
Date: Tue, 20 Feb 2018 08:39:28 +0100 (CET) [thread overview]
Message-ID: <20180220073928.77B341B1BC@dpdk.org> (raw)
In-Reply-To: <1519112078-20113-3-git-send-email-arybchenko@solarflare.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/35241
_coding style issues_
WARNING:LONG_LINE_COMMENT: line over 90 characters
#34: FILE: drivers/net/sfc/base/siena_flash.h:106:
+ efx_dword_t security_level; /* This number increases every time a serious security flaw */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#35: FILE: drivers/net/sfc/base/siena_flash.h:107:
+ /* is fixed. A secure NIC may not downgrade to any image */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#36: FILE: drivers/net/sfc/base/siena_flash.h:108:
+ /* with a lower security level than the current image. */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#37: FILE: drivers/net/sfc/base/siena_flash.h:109:
+ /* Note: The number in this header should only be used for */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#38: FILE: drivers/net/sfc/base/siena_flash.h:110:
+ /* determining the level of new images, not to determine */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#39: FILE: drivers/net/sfc/base/siena_flash.h:111:
+ /* the level of the current image as this header is not */
total: 0 errors, 6 warnings, 0 checks, 15 lines checked
parent reply other threads:[~2018-02-20 7:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1519112078-20113-3-git-send-email-arybchenko@solarflare.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=20180220073928.77B341B1BC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arybchenko@solarflare.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).