From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konrad Jankowski <konrad.jankowski@intel.com>
Subject: [dpdk-test-report] |WARNING| pw35183 [PATCH] net/i40evf: regression fix - reenable interrupts in handler
Date: Wed, 14 Feb 2018 19:30:00 +0100 (CET) [thread overview]
Message-ID: <20180214183000.C4B3E1B295@dpdk.org> (raw)
In-Reply-To: <1518633151-29118-1-git-send-email-konrad.jankowski@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/35183
_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")'
#15:
Commit 66b8304f removed the rte_intr_enable() call from
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#16:
i40evf_dev_interrupt_handler() as a "bonus". On one of my systems this causes
WARNING:TYPO_SPELLING: 'beeing' may be misspelled - perhaps 'being'?
#17:
the AdminQ messages to stop beeing delivered to the VF. This results in
total: 1 errors, 2 warnings, 0 checks, 7 lines checked
parent reply other threads:[~2018-02-14 18:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1518633151-29118-1-git-send-email-konrad.jankowski@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=20180214183000.C4B3E1B295@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konrad.jankowski@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).