automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw125474 [PATCH v2 6/7] net/null: replace rte atomics with GCC builtin atomics
Date: Thu, 23 Mar 2023 23:36:05 +0100 (CET)	[thread overview]
Message-ID: <20230323223605.821FC120A07@dpdk.org> (raw)
In-Reply-To: <1679610881-25997-7-git-send-email-roretzla@linux.microsoft.com>

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

_coding style issues_


ERROR:C99_COMMENTS: do not use C99 // comments
#82: FILE: drivers/net/null/rte_eth_null.c:104:
+	// NOTE: review for potential ordering optimization

ERROR:C99_COMMENTS: do not use C99 // comments
#92: FILE: drivers/net/null/rte_eth_null.c:132:
+	// NOTE: review for potential ordering optimization

ERROR:C99_COMMENTS: do not use C99 // comments
#102: FILE: drivers/net/null/rte_eth_null.c:157:
+	// NOTE: review for potential ordering optimization

ERROR:C99_COMMENTS: do not use C99 // comments
#112: FILE: drivers/net/null/rte_eth_null.c:180:
+	// NOTE: review for potential ordering optimization

ERROR:C99_COMMENTS: do not use C99 // comments
#121: FILE: drivers/net/null/rte_eth_null.c:323:
+		// NOTE: review for atomic access

ERROR:C99_COMMENTS: do not use C99 // comments
#132: FILE: drivers/net/null/rte_eth_null.c:333:
+		// NOTE: review for atomic access

ERROR:C99_COMMENTS: do not use C99 // comments
#144: FILE: drivers/net/null/rte_eth_null.c:356:
+		// NOTE: review for atomic access

ERROR:C99_COMMENTS: do not use C99 // comments
#148: FILE: drivers/net/null/rte_eth_null.c:359:
+		// NOTE: review for atomic access

total: 8 errors, 0 warnings, 0 checks, 79 lines checked

           reply	other threads:[~2023-03-23 22:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1679610881-25997-7-git-send-email-roretzla@linux.microsoft.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=20230323223605.821FC120A07@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=roretzla@linux.microsoft.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).