automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Mihai Brodschi <mihai.brodschi@broadcom.com>
Subject: |WARNING| pw141978 [PATCH] net/memif: fix buffer overflow in zero copy Rx
Date: Fri, 28 Jun 2024 21:47:02 +0200 (CEST)	[thread overview]
Message-ID: <20240628194702.09F44128144@dpdk.org> (raw)
In-Reply-To: <102781f4-e82c-4780-acb5-fad92fb2c30b@broadcom.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#87: 
Fixes: 43b815d88188 ("net/memif: support zero-copy slave")

WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#100: FILE: :1252:
+			/*

WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#101: FILE: :1253:
+			 * Allocate 2x ring_size to reserve a contiguous array for

WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#102: FILE: :1254:
+			 * rte_pktmbuf_alloc_bulk (to store allocated mbufs).

WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#103: FILE: :1255:
+			 */

WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#106: FILE: :1257:
+						  (1 << (mq->log2_ring_size + 1)), 0);

ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#117: FILE: drivers/net/memif/rte_eth_memif.c:599:
**bufs, uint16_t nb_pkts)

total: 1 errors, 6 warnings, 0 checks, 23 lines checked

  parent reply	other threads:[~2024-06-28 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <102781f4-e82c-4780-acb5-fad92fb2c30b@broadcom.com>
2024-06-28 19:18 ` qemudev
2024-06-28 19:47 ` checkpatch [this message]
2024-06-28 20:11 ` 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=20240628194702.09F44128144@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=mihai.brodschi@broadcom.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).