From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Cliff Burdick <cburdick@nvidia.com>
Subject: |WARNING| pw110529 [PATCH] gpu: add support for rtx 6000 variant
Date: Fri, 29 Apr 2022 18:53:44 +0200 (CEST) [thread overview]
Message-ID: <20220429165344.A8D301242B9@dpdk.org> (raw)
In-Reply-To: <BYAPR12MB359134D71AB0F853DCB1E9F8ABFC9@BYAPR12MB3591.namprd12.prod.outlook.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/110529
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#124: FILE: drivers/gpu/cuda/cuda.c:200:
+ NVIDIA_GPU_QUADRO_RTX_6000_1)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#124: FILE: drivers/gpu/cuda/cuda.c:200:
+ NVIDIA_GPU_QUADRO_RTX_6000_1)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#126: FILE: drivers/gpu/cuda/cuda.c:202:
+ {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#127: FILE: drivers/gpu/cuda/cuda.c:203:
+ RTE_PCI_DEVICE(NVIDIA_GPU_VENDOR_ID,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#127: FILE: drivers/gpu/cuda/cuda.c:203:
+ RTE_PCI_DEVICE(NVIDIA_GPU_VENDOR_ID,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#128: FILE: drivers/gpu/cuda/cuda.c:204:
+ NVIDIA_GPU_QUADRO_RTX_6000_2)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#128: FILE: drivers/gpu/cuda/cuda.c:204:
+ NVIDIA_GPU_QUADRO_RTX_6000_2)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#129: FILE: drivers/gpu/cuda/cuda.c:205:
+ },$
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#138: FILE: drivers/gpu/cuda/devices.h:51:
#define NVIDIA_GPU_GV100_QUADRO_DEVICE_ID (0x1dba)
ERROR:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Cliff Burdick <cburdick@nvidia.com>'
total: 5 errors, 5 warnings, 22 lines checked
next parent reply other threads:[~2022-04-29 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BYAPR12MB359134D71AB0F853DCB1E9F8ABFC9@BYAPR12MB3591.namprd12.prod.outlook.com>
2022-04-29 16:53 ` checkpatch [this message]
2022-04-29 17:08 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=20220429165344.A8D301242B9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=cburdick@nvidia.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).