diff options
| author | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-09-24 11:09:35 +0300 |
|---|---|---|
| committer | Mike Rapoport <rppt@kernel.org> | 2026-10-09 18:13:28 +0200 |
| commit | d5d21fffbff6d18fd9e746e31d8e5cdaff0f0b9d (patch) | |
| tree | f2cdd8a5c523495df470c2bebeada3947e13a066 /include/linux/platform_data | |
| parent | cee9395acd8043be0644b25c34bfa86623f2b935 (diff) | |
| parent | 10823ced2f18bd6779959744fb13e5974ca75a6a (diff) | |
| download | linux-next-d5d21fffbff6d18fd9e746e31d8e5cdaff0f0b9d.tar.gz linux-next-d5d21fffbff6d18fd9e746e31d8e5cdaff0f0b9d.zip | |
Merge patch series "kho: rename "scratch" to "bootmem""
Pratyush Yadav <pratyush@kernel.org> says:
kho: rename "scratch" to "bootmem"
From: "Pratyush Yadav (Google)" <pratyush@kernel.org>
The term "KHO scratch" is vague and overloaded. It does not accurately
describe what the memory is for. This was discussed previously at [0].
The conclusion was to rename "KHO scratch" to "KHO bootmem", since this
is memory passed by the previous kernel for early boot allocations.
In addition, memblock does not care about the provenance of the memory.
It cares more about how it should use it. Use MEMBLOCK_KHO_NOPRSRV,
instead of MEMBLOCK_KHO_SCRATCH, to describe this memory to memblock.
This series does the renames. It also gets rid of a redundant Kconfig.
While the diffstat is big and scary, most of the changes are mechanical.
* patches from https://patch.msgid.link/20260922041321.233986-1-pratyush@kernel.org
memblock: get rid of CONFIG_MEMBLOCK_KHO_SCRATCH
memblock: rename KHO_SCRATCH to KHO_NOPRSRV
kho: rename KHO scratch to KHO bootmem
kho: rename kho_scratch= commandline parameter to kho_bootmem=
Link: https://patch.msgid.link/20260922041321.233986-1-pratyush@kernel.org
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Diffstat (limited to 'include/linux/platform_data')
0 files changed, 0 insertions, 0 deletions