From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anoob Joseph <anoobj@marvell.com>
Subject: |WARNING| pw126116 [PATCH v2 16/22] pdcp: add timer expiry handle
Date: Fri, 14 Apr 2023 19:48:00 +0200 (CEST) [thread overview]
Message-ID: <20230414174800.E0C7B121EF4@dpdk.org> (raw)
In-Reply-To: <20230414174512.642-17-anoobj@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126116
_coding style issues_
WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#91:
and PDCP internal state variables (like RX_REORD, RX_DELIV etc) will be
WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#115: FILE: doc/guides/prog_guide/pdcp_lib.rst:236:
+transmitted in the packet. It utilizes state variables such as RX_REORD,
WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#167: FILE: lib/pdcp/pdcp_process.c:1304:
+ /* - all stored PDCP SDU(s) with associated COUNT value(s) < RX_REORD; */
WARNING:TYPO_SPELLING: 'reord' may be misspelled - perhaps 'record'?
#168: FILE: lib/pdcp/pdcp_process.c:1305:
+ nb_out = pdcp_reorder_up_to_get(&dl->reorder, out_mb, capacity, en_priv->state.rx_reord);
WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#174: FILE: lib/pdcp/pdcp_process.c:1311:
+ * RX_REORD;
WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#181: FILE: lib/pdcp/pdcp_process.c:1318:
+ * to upper layers, with COUNT value >= RX_REORD;
WARNING:TYPO_SPELLING: 'reord' may be misspelled - perhaps 'record'?
#183: FILE: lib/pdcp/pdcp_process.c:1320:
+ en_priv->state.rx_deliv = en_priv->state.rx_reord + nb_seq;
WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#187: FILE: lib/pdcp/pdcp_process.c:1324:
+ * - update RX_REORD to RX_NEXT;
WARNING:TYPO_SPELLING: 'reord' may be misspelled - perhaps 'record'?
#191: FILE: lib/pdcp/pdcp_process.c:1328:
+ en_priv->state.rx_reord = en_priv->state.rx_next;
WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#231: FILE: lib/pdcp/rte_pdcp.h:339:
+ * window by updating state variables such as RX_REORD & RX_DELIV. PDCP would
total: 0 errors, 10 warnings, 143 lines checked
parent reply other threads:[~2023-04-14 17:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230414174512.642-17-anoobj@marvell.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=20230414174800.E0C7B121EF4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anoobj@marvell.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).