From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Szwed, Maciej" <maciej.szwed@intel.com>
Subject: [dpdk-test-report] |WARNING| pw97230 [PATCH v2] eal: read data buffer on RTE_INTR_HANDLE_VFIO_REQ
Date: Mon, 23 Aug 2021 16:18:11 +0200 (CEST) [thread overview]
Message-ID: <20210823141811.785B91226B3@dpdk.org> (raw)
In-Reply-To: <BL0PR11MB29484DF93707E906EDFABEAD97C49@BL0PR11MB2948.namprd11.prod.outlook.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/97230
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#152: FILE: lib/eal/linux/eal_interrupts.c:919:
#ifdef VFIO_PRESENT
ERROR:CODE_INDENT: code indent should use tabs where possible
#154: FILE: lib/eal/linux/eal_interrupts.c:921:
+ case RTE_INTR_HANDLE_VFIO_REQ:$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#154: FILE: lib/eal/linux/eal_interrupts.c:921:
+ case RTE_INTR_HANDLE_VFIO_REQ:$
ERROR:CODE_INDENT: code indent should use tabs where possible
#155: FILE: lib/eal/linux/eal_interrupts.c:922:
+ call = true;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#155: FILE: lib/eal/linux/eal_interrupts.c:922:
+ call = true;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#157: FILE: lib/eal/linux/eal_interrupts.c:924:
+ /* fall through */$
WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email name mismatch: 'From: "Szwed, Maciej" <maciej.szwed@intel.com>' != 'Signed-off-by: Maciej Szwed <maciej.szwed@intel.com>'
total: 4 errors, 3 warnings, 22 lines checked
next parent reply other threads:[~2021-08-23 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BL0PR11MB29484DF93707E906EDFABEAD97C49@BL0PR11MB2948.namprd11.prod.outlook.com>
2021-08-23 14:18 ` checkpatch [this message]
2021-08-23 14:43 [dpdk-test-report] |WARNING| pw97230 [PATCH] [v2] " dpdklab
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=20210823141811.785B91226B3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=maciej.szwed@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).