Usage of 0x10000 in the inverted weight calculation causes overflow of uint16_t 
if weight=1.
As a result of this bug, frame len used for virtual finish time calculation is 
always zero, despite of packet size, so packets from input with weight=1 always 
pass first.
Signed-off-by: Dmitriy Krot [email protected]

----------------github------------------------
/** Email created from pull request 21 (dkrot:master)
 ** https://github.com/Linaro/odp/pull/21
 ** Patch: https://github.com/Linaro/odp/pull/21.patch
 ** Base sha: 79ba737a404d2833ad33d8f84ed6ce82c9a8c18e
 ** Merge commit sha: 52076413a304fa921e43dbbb64e4fa1989f2cabc
 **/
----------------/github------------------------

----------------checkpatch.pl------------------------
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per 
line)
#7: 
Usage of 0x10000 in the inverted weight calculation causes overflow of uint16_t 
if weight=1.

total: 0 errors, 1 warnings, 0 checks, 16 lines checked


to_send-p-000.patch has style problems, please review.

If any of these errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
----------------/checkpatch.pl------------------------

Reply via email to