|WARNING| pw126116 [PATCH v2 16/22] pdcp: add timer expiry handle

[checkpatch at dpdk.org]

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