automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Vipin P R <vipinp@vmware.com>
Subject: |WARNING| pw122077 [PATCH 1/2] Memory Allocation: Fixes ignore_msk during find_next_n in fb_array library
Date: Sun, 15 Jan 2023 21:13:30 +0100 (CET)	[thread overview]
Message-ID: <20230115201330.934A1123659@dpdk.org> (raw)
In-Reply-To: <1673615669-21011-2-git-send-email-vipinp@vmware.com>

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

_coding style issues_


ERROR:TRAILING_WHITESPACE: trailing whitespace
#128: FILE: lib/eal/common/eal_common_fbarray.c:239:
+^I^I^I^I^I/* There aren't "need" number of contiguous bits anywhere in the mask. $

WARNING:LONG_LINE_COMMENT: line length of 111 exceeds 100 columns
#128: FILE: lib/eal/common/eal_common_fbarray.c:239:
+					/* There aren't "need" number of contiguous bits anywhere in the mask. 

ERROR:TRAILING_WHITESPACE: trailing whitespace
#129: FILE: lib/eal/common/eal_common_fbarray.c:240:
+^I^I^I^I^I * Ignore these many number of bits from LSB for the next iteration. $

WARNING:LONG_LINE_COMMENT: line length of 109 exceeds 100 columns
#129: FILE: lib/eal/common/eal_common_fbarray.c:240:
+					 * Ignore these many number of bits from LSB for the next iteration. 

total: 2 errors, 2 warnings, 13 lines checked
Vipin P R <vipinp@vmware.com> is unknown, please fix the commit message or update .mailmap.
Kumara Parameshwaran mail differs from primary mail, please fix the commit message or update .mailmap.

      parent reply	other threads:[~2023-01-15 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1673615669-21011-2-git-send-email-vipinp@vmware.com>
2023-01-15 20:08 ` |WARNING| pw122077-122078 [PATCH 1/2] Memory Allocation: Fixes ignore_msk during find_next_n() " qemudev
2023-01-15 20:13 ` checkpatch [this message]

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=20230115201330.934A1123659@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=vipinp@vmware.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).