summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorSean Rhodes <sean@starlabs.systems>2026-09-01 18:48:03 +0100
committerTzung-Bi Shih <tzungbi@kernel.org>2026-09-02 09:24:30 +0000
commit44e33a5aaa2de3f5cf2701d6f4b0a7c63d4fe602 (patch)
treed204a73915a0ba8fade7ad4fdbae724426938c00 /scripts/Makefile.thinlto
parentcee9395acd8043be0644b25c34bfa86623f2b935 (diff)
downloadlinux-next-44e33a5aaa2de3f5cf2701d6f4b0a7c63d4fe602.tar.gz
linux-next-44e33a5aaa2de3f5cf2701d6f4b0a7c63d4fe602.zip
firmware: Rename google firmware directory to coreboot
Most drivers in drivers/firmware/google are coreboot table drivers rather than Google-specific firmware drivers. Rename the directory to coreboot and update the Kconfig prompt, build path and maintainer entry. Rename the generic firmware Kconfig symbols to CONFIG_COREBOOT_* at the same time so new configurations describe the firmware interface rather than one vendor. Keep the old CONFIG_GOOGLE_* names as transitional symbols so existing configurations keep selecting the same drivers during the rename. Leave defconfig updates to a separate patch so the configuration churn is easy to review independently. Suggested-by: Julius Werner <jwerner@chromium.org> Signed-off-by: Sean Rhodes <sean@starlabs.systems> Link: https://lore.kernel.org/r/0a81e0d8e15c13f6a65c45ce476e37b33564ad61.1788284852.git.sean@starlabs.systems Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions