automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Michal Krawczyk <mk@semihalf.com>
Subject: [dpdk-test-report] |WARNING| pw56497 [PATCH v2] net/ena: update version to 2.0.1
Date: Tue, 16 Jul 2019 13:01:30 +0200 (CEST)	[thread overview]
Message-ID: <20190716110130.291D11B950@dpdk.org> (raw)
In-Reply-To: <20190716105956.15827-1-mk@semihalf.com>

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

_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")'
#19: 
    - 4217cb0b7d2c ("net/ena: fix assigning NUMA node to IO queue")

ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#22: 
    - ef74b5f7b69b ("net/ena: fix Rx checksum errors statistics")

ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#23: 
    - 5673e285a633 ("net/ena: fix Tx statistics")

ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#25: 
    - 117ba4a60488 ("net/ena: get device info statically")

ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#27: 
    - ef538c1a7f56 ("net/ena: fix checksum feature flag")

total: 5 errors, 0 warnings, 0 checks, 8 lines checked

           reply	other threads:[~2019-07-16 11:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190716105956.15827-1-mk@semihalf.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=20190716110130.291D11B950@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=mk@semihalf.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).