From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Subject: [dpdk-test-report] |WARNING| pw25322 [PATCH] net/mlx5: fix creation of drop flows
Date: Thu, 15 Jun 2017 10:26:39 +0200 (CEST) [thread overview]
Message-ID: <20170615082639.479642BF1@dpdk.org> (raw)
In-Reply-To: <3939c03cb081af386ad990f5efb2b0758623ac6f.1497515081.git.nelio.laranjeiro@6wind.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/25322
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#16:
Drop flows being created when the port is stop should not access to the drop
total: 0 errors, 1 warnings, 0 checks, 10 lines checked
parent reply other threads:[~2017-06-15 8:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3939c03cb081af386ad990f5efb2b0758623ac6f.1497515081.git.nelio.laranjeiro@6wind.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=20170615082639.479642BF1@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nelio.laranjeiro@6wind.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).