|WARNING| pw127618 [PATCH v5 16/21] pdcp: add timer expiry handle

[checkpatch@dpdk.org]

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

_coding style issues_


WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#92: 
and PDCP internal state variables (like RX_REORD, RX_DELIV etc) will be

WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#116: FILE: doc/guides/prog_guide/pdcp_lib.rst:137:
+transmitted in the packet. It utilizes state variables such as RX_REORD,

WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#169: FILE: lib/pdcp/rte_pdcp.c:270:
+	/*   - all stored PDCP SDU(s) with associated COUNT value(s) < RX_REORD; */

WARNING:TYPO_SPELLING: 'reord' may be misspelled - perhaps 'record'?
#170: FILE: lib/pdcp/rte_pdcp.c:271:
+	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'?
#176: FILE: lib/pdcp/rte_pdcp.c:277:
+	 *     RX_REORD;

WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#183: FILE: lib/pdcp/rte_pdcp.c:284:
+	 *   to upper layers, with COUNT value >= RX_REORD;

WARNING:TYPO_SPELLING: 'reord' may be misspelled - perhaps 'record'?
#185: FILE: lib/pdcp/rte_pdcp.c:286:
+	en_priv->state.rx_deliv = en_priv->state.rx_reord + nb_seq;

WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#189: FILE: lib/pdcp/rte_pdcp.c:290:
+	 *   - update RX_REORD to RX_NEXT;

WARNING:TYPO_SPELLING: 'reord' may be misspelled - perhaps 'record'?
#193: FILE: lib/pdcp/rte_pdcp.c:294:
+		en_priv->state.rx_reord = en_priv->state.rx_next;

WARNING:TYPO_SPELLING: 'REORD' may be misspelled - perhaps 'RECORD'?
#233: FILE: lib/pdcp/rte_pdcp.h:351:
+ * window by updating state variables such as RX_REORD & RX_DELIV. PDCP would

total: 0 errors, 10 warnings, 144 lines checked