automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Jyoti, Anand B" <anand.b.jyoti@intel.com>
Subject: [dpdk-test-report] |WARNING| pw18981 [PATCH] examples/ip_pipeline: check vlan and mpls params
Date: Fri,  6 Jan 2017 18:21:55 +0100 (CET)	[thread overview]
Message-ID: <20170106172155.5DA362B9C@dpdk.org> (raw)
In-Reply-To: <A1F25702B3CE3F4F8D3936A55AD1FF37925DB5F9@BGSMSX108.gar.corp.intel.com>

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

_coding style issues_


ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#55: 
>From e346e359ed9c5e8261f09f93629bff56d7c10a11 Mon Sep 17 00:00:00 2001

ERROR:SPACING: spaces required around that '=' (ctx:WxV)
#98: FILE: examples/ip_pipeline/pipeline/pipeline_routing.c:513:
+			for (i =3D 0; i < data->l2.mpls.n_labels; i++)
 			       ^

ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#104: FILE: examples/ip_pipeline/pipeline/pipeline_routing.c:518:
=20

total: 3 errors, 0 warnings, 29 lines checked

           reply	other threads:[~2017-01-06 17:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <A1F25702B3CE3F4F8D3936A55AD1FF37925DB5F9@BGSMSX108.gar.corp.intel.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=20170106172155.5DA362B9C@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=anand.b.jyoti@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).