diff options
author | Tom Rini <trini@konsulko.com> | 2025-01-20 19:18:36 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2025-01-20 19:26:55 -0600 |
commit | 5d5ce5f25708077e354a5627ec92b643145992cc (patch) | |
tree | 705999bad53f56f262b455d435952e78df395829 /drivers/fpga/intel_sdm_mb.c | |
parent | 9bfc72e3b2af4d426e712fe8d8165ebd1dcf74b9 (diff) | |
parent | 3e6fc0fa7b6af37c18a5532a9f2977c68ad948ec (diff) |
Merge patch series "Rework the BLK symbol usage in Kconfig"
Tom Rini <trini@konsulko.com> says:
One problem we have today is how the BLK symbol is set and used in
Kconfig files. Part of the challenge is that we use it as a gating
symbol for "we have a block device" and also for "enable block device
library code". What this series does is move to always use "select BLK"
by block drivers (a few were and a few others had it the inverse) and
then "depends on BLK" for functionality that needs a block device
present. The end result of this series is that a number of platforms
which had disabled EFI_LOADER now don't ask for it (they have no block
device) and espresso7420 has a regression about MMC support fixed. With
v2 of this I've picked up the review tags from v1 and also reworded the
body of the commit in the first patch.
Link: https://lore.kernel.org/r/20250115012322.215243-1-trini@konsulko.com
Diffstat (limited to 'drivers/fpga/intel_sdm_mb.c')
0 files changed, 0 insertions, 0 deletions