As we walk the results of largest_resource(), we actually know that the condition can only be true for the first return value. So there's no need to keep track of the first loop iteration.
Change-Id: I6d6b99e38706c0c70f3570222d97a1d71ba79744
74169c1c71 allocator_v4: Make it explicit that we start with the highest alignment
src/device/resource_allocator_v4.c | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
Upstream: review.coreboot.org