From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Subject: [dpdk-test-report] |WARNING| pw39041 [PATCH] lcore: make semantics of lcore role function more intuitive
Date: Thu, 26 Apr 2018 16:45:47 +0200 (CEST) [thread overview]
Message-ID: <20180426144547.E84F38E5B@dpdk.org> (raw)
In-Reply-To: <BE54F058557D9A4FAC1D84E2FC6D87570EE2DACC@fmsmsx115.amr.corp.intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/39041
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#19:
Thanks, Anatoly and Thomas. I had also considered the following chunk for the release notes:
ERROR:TRAILING_WHITESPACE: trailing whitespace
#71: FILE: doc/guides/rel_notes/release_18_05.rst:75:
+* **rte_lcore_has_role() return values changed** $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#72: FILE: doc/guides/rel_notes/release_18_05.rst:76:
+ $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#73: FILE: doc/guides/rel_notes/release_18_05.rst:77:
+ This function now returns 1 or 0 for true or false, respectively, rather $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#74: FILE: doc/guides/rel_notes/release_18_05.rst:78:
+ than 0 or <0 for success or failure to make use of the function more $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#75: FILE: doc/guides/rel_notes/release_18_05.rst:79:
+ intuitive. $
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 6 errors, 1 warnings, 11 lines checked
parent reply other threads:[~2018-04-26 14:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BE54F058557D9A4FAC1D84E2FC6D87570EE2DACC@fmsmsx115.amr.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=20180426144547.E84F38E5B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=erik.g.carrillo@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).