summaryrefslogtreecommitdiff
path: root/config/grub/xhci/patches/0013-don-t-print-empty-error-messages.patch
diff options
context:
space:
mode:
authorLeah Rowe <info@minifree.org>2024-08-11 21:19:33 +0100
committerLeah Rowe <leah@libreboot.org>2024-08-11 21:22:26 +0100
commitd66f6e0d5bf941e70f9126c19fb5608a3bbb4ade (patch)
treeffb206f45c6ea22307e132baac463f80d4dd3306 /config/grub/xhci/patches/0013-don-t-print-empty-error-messages.patch
parentaae8cabe73675b0a2d15199ec5e1504837cd4080 (diff)
vendor.sh: don't load entire coreboot configs
instead, only grep for the entries required, such as Intel ME paths. some variables in coreboot configs use $(), which is used in *make*, on the coreboot build system, and there refers to variables. here, we are sourcing them from sh, which treats this as a mini subshell to run a command; for example CONFIG_FOO would be executed, which is bad. The current logic still theoretically has this problem, with this patch, but the entries we scan from the configs do not currently have variable names in the strings. So: filter out just what we need, into a temporary config, when scanning for vendor files in coreboot configs, and use the temporary config. This fixes a build error when compiling for e5520_6mb. Signed-off-by: Leah Rowe <info@minifree.org>
Diffstat (limited to 'config/grub/xhci/patches/0013-don-t-print-empty-error-messages.patch')
0 files changed, 0 insertions, 0 deletions