automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Robin Jarry <rjarry@redhat.com>
Subject: |WARNING| pw131972 [RFC PATCH] usertools: add telemetry exporter
Date: Tue, 26 Sep 2023 18:35:51 +0200 (CEST)	[thread overview]
Message-ID: <20230926163551.5021B120999@dpdk.org> (raw)
In-Reply-To: <20230926163442.844006-2-rjarry@redhat.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#143: 
Link: https://github.com/influxdata/telegraf/tree/master/plugins/inputs/prometheus

WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#406: FILE: usertools/dpdk-telemetry-exporter.py:228:
+    dwb = sys.dont_write_bytecode

WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#407: FILE: usertools/dpdk-telemetry-exporter.py:229:
+    sys.dont_write_bytecode = True  # never generate .pyc files for endpoints

WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#431: FILE: usertools/dpdk-telemetry-exporter.py:253:
+    sys.dont_write_bytecode = dwb

WARNING:TYPO_SPELLING: 'uppon' may be misspelled - perhaps 'upon'?
#479: FILE: usertools/dpdk-telemetry-exporter.py:301:
+        Called uppon GET requests.

total: 0 errors, 5 warnings, 500 lines checked

      parent reply	other threads:[~2023-09-26 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230926163442.844006-2-rjarry@redhat.com>
2023-09-26 16:16 ` |SUCCESS| " qemudev
2023-09-26 16:20 ` qemudev
2023-09-26 16:35 ` checkpatch [this message]

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=20230926163551.5021B120999@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=rjarry@redhat.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).