automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: nickcooper-zhangtonghao <nic@opencloud.tech>
Subject: [dpdk-test-report] |WARNING| pw18904 [PATCH 1/5] NUMA: Set numa node value for system which not support NUMA.
Date: Thu,  5 Jan 2017 11:43:36 +0100 (CET)	[thread overview]
Message-ID: <20170105104336.CA94FF91E@dpdk.org> (raw)
In-Reply-To: <1483612983-3545-1-git-send-email-nic@opencloud.tech>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#64: FILE: lib/librte_eal/linuxapp/eal/eal_pci.c:320:
+        /* The NUMA node information for PCI devices provided through$

ERROR:CODE_INDENT: code indent should use tabs where possible
#65: FILE: lib/librte_eal/linuxapp/eal/eal_pci.c:321:
+         * sysfs is invalid for AMD Opteron(TM) Processor 62xx and 63xx$

ERROR:CODE_INDENT: code indent should use tabs where possible
#66: FILE: lib/librte_eal/linuxapp/eal/eal_pci.c:322:
+         * on Red Hat Enterprise Linux 6, and VMs on some hypervisors.$

ERROR:CODE_INDENT: code indent should use tabs where possible
#67: FILE: lib/librte_eal/linuxapp/eal/eal_pci.c:323:
+         * In the upstream linux kernel, the numa_node is an integer,$

ERROR:CODE_INDENT: code indent should use tabs where possible
#68: FILE: lib/librte_eal/linuxapp/eal/eal_pci.c:324:
+         * which data type is int, not unsigned long.$

ERROR:CODE_INDENT: code indent should use tabs where possible
#69: FILE: lib/librte_eal/linuxapp/eal/eal_pci.c:325:
+         */$

total: 6 errors, 0 warnings, 14 lines checked

           reply	other threads:[~2017-01-05 10:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1483612983-3545-1-git-send-email-nic@opencloud.tech>]

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=20170105104336.CA94FF91E@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=nic@opencloud.tech \
    --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).