From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: [dpdk-test-report] |WARNING| pw22922 [PATCH 0/9] mbuf: structure reorganization
Date: Thu, 30 Mar 2017 20:07:29 +0200 (CEST) [thread overview]
Message-ID: <20170330180729.04DEF376F@dpdk.org> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772583FAE2B2F@IRSMSX109.ger.corp.intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/22922
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#24:
> To: Ananyev, Konstantin <konstantin.ananyev@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>; Olivier Matz
WARNING:TYPO_SPELLING: 'noticable' may be misspelled - perhaps 'noticeable'?
#72:
> > > > > fairly noticable performance drop. I still need to dig in more, e.g. do
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 2 warnings, 22 lines checked
parent reply other threads:[~2017-03-30 18:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2601191342CEEE43887BDE71AB9772583FAE2B2F@IRSMSX109.ger.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=20170330180729.04DEF376F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konstantin.ananyev@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).