automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-test-report] |WARNING| pw77599 [PATCH] eal: detach memsegs on cleanup
Date: Mon, 14 Sep 2020 13:18:26 +0200 (CEST)	[thread overview]
Message-ID: <20200914111826.D5C801C0C0@dpdk.org> (raw)
In-Reply-To: <cab1b8bcc35a164d6683118985412d937aec137b.1600081980.git.anatoly.burakov@intel.com>

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

_coding style issues_


WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#103: FILE: lib/librte_eal/common/eal_common_memory.c:1011:
+	unsigned i;

WARNING:TYPO_SPELLING: 'subsytem' may be misspelled - perhaps 'subsystem'?
#107: FILE: lib/librte_eal/common/eal_common_memory.c:1015:
+	/* detach internal memory subsytem data first */

total: 0 errors, 2 warnings, 237 lines checked

       reply	other threads:[~2020-09-14 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cab1b8bcc35a164d6683118985412d937aec137b.1600081980.git.anatoly.burakov@intel.com>
2020-09-14 11:18 ` checkpatch [this message]
2020-09-14 13:56 ` [dpdk-test-report] || pw77599 " 0-day Robot

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=20200914111826.D5C801C0C0@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=anatoly.burakov@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).