automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: [dpdk-test-report] |WARNING| pw53169 [PATCH] app/compress-perf: add info about socket id used by app and by the driver
Date: Tue, 30 Apr 2019 19:10:36 +0200 (CEST)	[thread overview]
Message-ID: <20190430171036.E30865B12@dpdk.org> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B4358974F68C@IRSMSX101.ger.corp.intel.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#19: 
Added info about socket id used by compression perf test process and by the driver

WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Trahe, Fiona <fiona.trahe@intel.com>'

total: 0 errors, 2 warnings, 9 lines checked

           reply	other threads:[~2019-04-30 17:10 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <348A99DA5F5B7549AA880327E580B4358974F68C@IRSMSX101.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=20190430171036.E30865B12@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=fiona.trahe@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).