|WARNING| pw122073 [PATCH 1/2] Memory Allocation: Fixes ms_idx jump lookahead during find_next_n in fb_array library

[checkpatch at dpdk.org]

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#104: 
In the legacy mem mode, when the fb_array is being populated, if there are holes in between, the ms_idx could go backward and there will be an overlap of the region starting from the ms_idx returned later. i.e. it's being mapped to two different physical regions in PA space to a contiguous region in VA space. this would result in the allocator assuming that the memory is contiguous even though there is a hole in between. In legacy mem, allocator assumes that PA contiguous are VA contiguous as well.

total: 0 errors, 1 warnings, 15 lines checked
Vipin P R <vipinp at vmware.com> is unknown, please fix the commit message or update .mailmap.
Kumara Parameshwaran mail differs from primary mail, please fix the commit message or update .mailmap.