From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Mykola Kostenok <mko-plv@napatech.com>
Subject: |WARNING| pw130540 [PATCH v4 4/8] net/ntnic: adds flow related FPGA functionality
Date: Fri, 18 Aug 2023 21:00:37 +0200 (CEST) [thread overview]
Message-ID: <20230818190037.7FEAA1206AB@dpdk.org> (raw)
In-Reply-To: <20230818184127.422574-4-mko-plv@napatech.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/130540
_coding style issues_
WARNING:TYPO_SPELLING: 'uis' may be misspelled - perhaps 'is'?
#2031: FILE: drivers/net/ntnic/nthw/flow_filter/flow_nthw_flm.c:69:
+ p->mp_control_uis = register_get_field(p->mp_control, FLM_CONTROL_UIS);
WARNING:TYPO_SPELLING: 'UIS' may be misspelled - perhaps 'IS'?
#2031: FILE: drivers/net/ntnic/nthw/flow_filter/flow_nthw_flm.c:69:
+ p->mp_control_uis = register_get_field(p->mp_control, FLM_CONTROL_UIS);
WARNING:TYPO_SPELLING: 'uis' may be misspelled - perhaps 'is'?
#2272: FILE: drivers/net/ntnic/nthw/flow_filter/flow_nthw_flm.c:310:
+void flm_nthw_control_uis(const struct flm_nthw *p, uint32_t val)
WARNING:TYPO_SPELLING: 'uis' may be misspelled - perhaps 'is'?
#2274: FILE: drivers/net/ntnic/nthw/flow_filter/flow_nthw_flm.c:312:
+ field_set_val32(p->mp_control_uis, val);
WARNING:TYPO_SPELLING: 'uis' may be misspelled - perhaps 'is'?
#3135: FILE: drivers/net/ntnic/nthw/flow_filter/flow_nthw_flm.h:27:
+void flm_nthw_control_uis(const struct flm_nthw *p, uint32_t val);
WARNING:TYPO_SPELLING: 'uis' may be misspelled - perhaps 'is'?
#3362: FILE: drivers/net/ntnic/nthw/flow_filter/flow_nthw_flm.h:254:
+ nt_field_t *mp_control_uis;
total: 0 errors, 6 warnings, 0 checks, 8743 lines checked
parent reply other threads:[~2023-08-18 19:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230818184127.422574-4-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=20230818190037.7FEAA1206AB@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).