memrange: Update comment to indicate limit is inclusive for memranges_next_entry
This change updates the comment for memranges_next_entry() to indicate that the limit provided by the caller is inclusive. Change-Id: Id40263efcb9417ed31c130996e56c30dbbc82e02 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/41103 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
parent
1efa7d9093
commit
8211bde9c2
|
@ -162,7 +162,7 @@ struct range_entry *memranges_next_entry(struct memranges *ranges,
|
|||
const struct range_entry *r);
|
||||
|
||||
/* Steals memory from the available list in given ranges as per the constraints:
|
||||
* limit = Upper bound for the memory range to steal.
|
||||
* limit = Upper bound for the memory range to steal (Inclusive).
|
||||
* size = Requested size for the stolen memory.
|
||||
* align = Required alignment(log 2) for the starting address of the stolen memory.
|
||||
* tag = Use a range that matches the given tag.
|
||||
|
|
Loading…
Reference in New Issue