automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <eagostini@nvidia.com>
Subject: |WARNING| pw107899 [PATCH v2] gpu/cuda: CPU map GPU memory with GDRCopy
Date: Mon, 21 Feb 2022 15:35:28 +0100 (CET)	[thread overview]
Message-ID: <20220221143528.2023112336A@dpdk.org> (raw)
In-Reply-To: <20220221224433.26096-1-eagostini@nvidia.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'retun' may be misspelled - perhaps 'return'?
#178: FILE: doc/guides/gpus/cuda.rst:57:
+and will retun error if the application invokes the gpude ``rte_gpu_mem_cpu_map`` function.

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#363: FILE: drivers/gpu/cuda/gdrcopy.c:2:
+/* SPDX-License-Identifier: BSD-3-Clause
+* Copyright (c) 2022 NVIDIA Corporation & Affiliates

WARNING:LONG_LINE: line length of 132 exceeds 100 columns
#378: FILE: drivers/gpu/cuda/gdrcopy.c:17:
+static int (*sym_gdr_pin_buffer)(gdr_t g, unsigned long addr, size_t size, uint64_t p2p_token, uint32_t va_space, gdr_mh_t *handle);

WARNING:LONG_LINE: line length of 103 exceeds 100 columns
#544: FILE: drivers/gpu/cuda/gdrcopy.h:23:
+int gdrcopy_pin(gdr_t *gdrc_h, __rte_unused gdr_mh_t *mh, uint64_t d_addr, size_t size, void **h_addr);

total: 0 errors, 4 warnings, 380 lines checked

       reply	other threads:[~2022-02-21 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220221224433.26096-1-eagostini@nvidia.com>
2022-02-21 14:35 ` checkpatch [this message]
2022-02-21 16:19 ` |FAILURE| " 0-day Robot

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=20220221143528.2023112336A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=eagostini@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).