automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Mykola Kostenok <mko-plv@napatech.com>
Subject: |WARNING| pw130541 [PATCH v4 6/8] net/ntnic: adds flow logic
Date: Fri, 18 Aug 2023 20:54:02 +0200 (CEST)	[thread overview]
Message-ID: <20230818185402.A86001206AB@dpdk.org> (raw)
In-Reply-To: <20230818184127.422574-6-mko-plv@napatech.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#302: FILE: drivers/net/ntnic/nthw/flow_api/flow_api.c:5:
+#include <stdio.h>

WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#1911: FILE: drivers/net/ntnic/nthw/flow_api/flow_api_profile_inline.c:5:
+#include <stdio.h>

WARNING:TYPO_SPELLING: 'UIS' may be misspelled - perhaps 'IS'?
#6324: FILE: drivers/net/ntnic/nthw/flow_api/flow_api_profile_inline.c:4418:
+		hw_mod_flm_control_set(&ndev->be, HW_FLM_CONTROL_UIS,

WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#7122: FILE: drivers/net/ntnic/nthw/flow_filter/flow_backend.c:30:
+#include <stdio.h> /* printf */

WARNING:TYPO_SPELLING: 'uis' may be misspelled - perhaps 'is'?
#8385: FILE: drivers/net/ntnic/nthw/flow_filter/flow_backend.c:1293:
+		flm_nthw_control_uis(be->p_flm_nthw, flm->v17.control->uis);

WARNING:TYPO_SPELLING: 'uis' may be misspelled - perhaps 'is'?
#8385: FILE: drivers/net/ntnic/nthw/flow_filter/flow_backend.c:1293:
+		flm_nthw_control_uis(be->p_flm_nthw, flm->v17.control->uis);

total: 0 errors, 6 warnings, 0 checks, 10151 lines checked

           reply	other threads:[~2023-08-18 18:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230818184127.422574-6-mko-plv@napatech.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=20230818185402.A86001206AB@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=mko-plv@napatech.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).