|WARNING| pw160117 [PATCH v4 6/6] test/soring: fix stringop-overflow warning with LTO

[checkpatch at dpdk.org]

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

_coding style issues_


WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#72: 
Subject: [PATCH v4 6/6] test/soring: fix stringop-overflow warning with LTO
                             ^^^^^^

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#93: 
When LTO is enabled, GCC inlines through the soring dequeue path into
                                             ^^^^^^

WARNING:TYPO_SPELLING: 'propogate' may be misspelled - perhaps 'propagate'?
#107: 
resolve the problem because the condition does not propogate
                                                   ^^^^^^^^^

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#116: 
Fixes: 70581c355d69 ("test/ring: add unit tests for soring API")
                                                    ^^^^^^

WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#139: FILE: app/test/test_soring.c:153:
+	 * The soring/ring code has paths for 4/8/16-byte elements.
 	       ^^^^^^

total: 0 errors, 5 warnings, 24 lines checked