diff options
| author | Elyes HAOUAS <ehaouas@noos.fr> | 2021-02-03 20:18:03 +0100 |
|---|---|---|
| committer | Patrick Georgi <pgeorgi@google.com> | 2021-02-05 09:40:39 +0000 |
| commit | 9c55c37a185ec4a6e2baf22021961877e43169eb (patch) | |
| tree | 44c4383f12da58b8750b38a1509517b6ee46935f | |
| parent | ee25a6fb0e4bd2e43ce2e120c83b609e1aff32b6 (diff) | |
payloads/libpayload/arch/arm64/mmu.c: Fix typo in comment
Change-Id: Ieb10a881ef1d983f11318f0f6934491fd19fd0bf
Signed-off-by: Elyes HAOUAS <ehaouas@noos.fr>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/50268
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Julius Werner <jwerner@chromium.org>
| -rw-r--r-- | payloads/libpayload/arch/arm64/mmu.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/payloads/libpayload/arch/arm64/mmu.c b/payloads/libpayload/arch/arm64/mmu.c index bc4c233479..4c8f8c15a8 100644 --- a/payloads/libpayload/arch/arm64/mmu.c +++ b/payloads/libpayload/arch/arm64/mmu.c @@ -389,7 +389,7 @@ struct mmu_new_range_prop { /* * Func: mmu_is_range_free - * Desc: We need to ensure that the new range being allocated doesnt overlap + * Desc: We need to ensure that the new range being allocated doesn't overlap * with any used memory range. Basically: * 1. Memory ranges used by the payload (usedmem_ranges) * 2. Any area that falls below _end symbol in linker script (Kernel needs to be |