automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>
Subject: [dpdk-test-report] |WARNING| pw35298 [PATCH 78/80] net/sfc/base: add firmware image layout option
Date: Tue, 20 Feb 2018 08:50:09 +0100 (CET)	[thread overview]
Message-ID: <20180220075009.5349D23A@dpdk.org> (raw)
In-Reply-To: <1519112078-20113-79-git-send-email-arybchenko@solarflare.com>

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

_coding style issues_


WARNING:LEADING_SPACE: please, no spaces at the start of a line
#97: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:25:
+  SIGNED_IMAGE_CHUNK_CMS_HEADER,        /* CMS header describing the signed data */$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#98: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:26:
+  SIGNED_IMAGE_CHUNK_REFLASH_HEADER,    /* Reflash header */$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#99: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:27:
+  SIGNED_IMAGE_CHUNK_IMAGE,             /* Bootable binary image */$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#100: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:28:
+  SIGNED_IMAGE_CHUNK_REFLASH_TRAILER,   /* Reflash trailer */$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#101: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:29:
+  SIGNED_IMAGE_CHUNK_SIGNATURE,         /* Remaining contents of the signed image,$

ERROR:CODE_INDENT: code indent should use tabs where possible
#102: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:30:
+                                         * including the certifiates and signature */$

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#102: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:30:
+                                         * including the certifiates and signature */

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#103: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:31:
+  NUM_SIGNED_IMAGE_CHUNKS,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#121: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:49:
+  uint32_t magic;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#123: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:51:
+  uint32_t version;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#125: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:53:
+  uint32_t id;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#127: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:55:
+  uint32_t offset;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#129: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:57:
+  uint32_t len;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#131: FILE: drivers/net/sfc/base/ef10_signed_image_layout.h:59:
+  uint32_t reserved[3];$

total: 1 errors, 13 warnings, 0 checks, 116 lines checked

           reply	other threads:[~2018-02-20  7:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1519112078-20113-79-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=20180220075009.5349D23A@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).