From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Robin Jarry <rjarry@redhat.com>
Subject: |WARNING| pw139419 [PATCH v2] usertools: add telemetry exporter
Date: Tue, 16 Apr 2024 15:48:17 +0200 (CEST) [thread overview]
Message-ID: <20240416134817.5700812083E@dpdk.org> (raw)
In-Reply-To: <20240416134620.64277-3-rjarry@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139419
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#149:
Link: https://github.com/influxdata/telegraf/tree/master/plugins/inputs/prometheus
WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#403: FILE: usertools/dpdk-telemetry-exporter.py:228:
+ dwb = sys.dont_write_bytecode
WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#404: 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:256:
+ sys.dont_write_bytecode = dwb
WARNING:TYPO_SPELLING: 'uppon' may be misspelled - perhaps 'upon'?
#482: FILE: usertools/dpdk-telemetry-exporter.py:307:
+ Called uppon GET requests.
total: 0 errors, 5 warnings, 529 lines checked
next prev parent reply other threads:[~2024-04-16 13:48 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240416134620.64277-3-rjarry@redhat.com>
2024-04-16 13:27 ` |SUCCESS| " qemudev
2024-04-16 13:31 ` qemudev
2024-04-16 13:48 ` checkpatch [this message]
2024-04-16 14:44 ` 0-day Robot
2024-04-16 16:47 ` |SUCCESS| pw139419 [PATCH] [v2] " dpdklab
2024-04-16 16:48 ` dpdklab
2024-04-16 16:48 ` dpdklab
2024-04-16 16:53 ` dpdklab
2024-04-16 17:06 ` dpdklab
2024-04-16 17:06 ` dpdklab
2024-04-16 17:07 ` dpdklab
2024-04-16 17:09 ` dpdklab
2024-04-16 17:09 ` dpdklab
2024-04-16 17:12 ` dpdklab
2024-04-16 17:14 ` dpdklab
2024-04-16 17:15 ` dpdklab
2024-04-16 17:15 ` dpdklab
2024-04-16 17:15 ` dpdklab
2024-04-16 17:16 ` dpdklab
2024-04-16 17:16 ` dpdklab
2024-04-16 17:16 ` dpdklab
2024-04-16 17:16 ` dpdklab
2024-04-16 17:16 ` dpdklab
2024-04-16 17:16 ` dpdklab
2024-04-16 17:16 ` dpdklab
2024-04-16 17:17 ` dpdklab
2024-04-16 17:17 ` dpdklab
2024-04-16 17:17 ` dpdklab
2024-04-16 17:22 ` dpdklab
2024-04-16 17:22 ` dpdklab
2024-04-16 17:23 ` dpdklab
2024-04-16 17:23 ` dpdklab
2024-04-16 17:23 ` dpdklab
2024-04-16 17:23 ` dpdklab
2024-04-16 17:23 ` dpdklab
2024-04-16 17:24 ` dpdklab
2024-04-16 17:24 ` dpdklab
2024-04-16 17:25 ` dpdklab
2024-04-16 17:25 ` dpdklab
2024-04-16 17:26 ` dpdklab
2024-04-16 17:27 ` dpdklab
2024-04-16 17:27 ` dpdklab
2024-04-16 17:27 ` dpdklab
2024-04-16 17:27 ` dpdklab
2024-04-16 17:28 ` dpdklab
2024-04-16 17:28 ` dpdklab
2024-04-16 17:28 ` dpdklab
2024-04-16 17:28 ` dpdklab
2024-04-16 17:29 ` dpdklab
2024-04-16 17:29 ` dpdklab
2024-04-16 17:29 ` dpdklab
2024-04-16 17:31 ` dpdklab
2024-04-16 17:43 ` dpdklab
2024-04-16 17:50 ` dpdklab
2024-04-16 17:50 ` dpdklab
2024-04-16 17:50 ` dpdklab
2024-04-16 17:50 ` dpdklab
2024-04-16 17:51 ` dpdklab
2024-04-16 17:51 ` dpdklab
2024-04-16 17:51 ` dpdklab
2024-04-16 17:52 ` dpdklab
2024-04-16 17:52 ` dpdklab
2024-04-16 17:52 ` dpdklab
2024-04-16 17:53 ` dpdklab
2024-04-16 17:54 ` dpdklab
2024-04-16 17:54 ` dpdklab
2024-04-16 17:55 ` dpdklab
2024-04-16 17:55 ` dpdklab
2024-04-16 17:55 ` dpdklab
2024-04-16 17:56 ` dpdklab
2024-04-16 17:56 ` dpdklab
2024-04-16 17:57 ` dpdklab
2024-04-16 17:57 ` dpdklab
2024-04-16 17:58 ` dpdklab
2024-04-16 17:58 ` dpdklab
2024-04-16 17:59 ` dpdklab
2024-04-16 17:59 ` dpdklab
2024-04-16 18:00 ` dpdklab
2024-04-16 18:00 ` dpdklab
2024-04-16 18:01 ` dpdklab
2024-04-16 18:01 ` dpdklab
2024-04-16 18:02 ` dpdklab
2024-04-16 18:03 ` dpdklab
2024-04-16 18:04 ` dpdklab
2024-04-16 18:04 ` dpdklab
2024-04-16 18:05 ` dpdklab
2024-04-16 18:07 ` dpdklab
2024-04-16 18:19 ` dpdklab
2024-04-16 18:21 ` dpdklab
2024-04-16 18:23 ` dpdklab
2024-04-16 18:31 ` dpdklab
2024-04-16 20:15 ` 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=20240416134817.5700812083E@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).