automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: jasvinder.singh@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw13460 ip_pipeline: fix false cacheline sharing among threads
Date: 11 Jun 2016 20:14:36 -0700	[thread overview]
Message-ID: <8dba68$tpq9mb@fmsmga002.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]


Test-Label: Intel Niantic on Fedora
Test-Status: ERROR

Patchwork ID: 13460
http://www.dpdk.org/dev/patchwork/patch/13460/
Submitter: Jasvinder Singh <jasvinder.singh@intel.com>
Date: Sat, 11 Jun 2016 16:19:16 +0100
DPDK git baseline: dd9ae4c7b302dffd9b3dac849f4da8badac91719

Check patch error:
13460: 
ERROR: space required after that close brace '}'
#36: FILE: examples/ip_pipeline/app.h:303:
+}__rte_cache_aligned;

total: 1 errors, 0 warnings, 8 lines checked

/home/patchWorkOrg/patches/dpdk-dev-ip_pipeline-fix-false-cacheline-sharing-among-threads.patch has style problems, please review.

If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS.


Compilation:
OS: fedora
Nic: niantic
GCC: gcc_x86-64, 4.8.3
ICC:16.0.2
i686-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-combined: compile pass
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-debug: compile pass
x86_64-native-linuxapp-gcc-shared: compile pass
x86_64-native-linuxapp-clang: compile pass



DPDK STV team 

                 reply	other threads:[~2016-06-12  3:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='8dba68$tpq9mb@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=jasvinder.singh@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).