Ard Biesheuvel <ardb@xxxxxxxxxx> writes: > The efivar layer is a caching non-volatile variable store abstraction > that is normally backed by EFI, but in some cases, might be backed by > Google SMI firmware interfaces instead. > > It is mainly used by efivarfs and EFI pstore, both of which actually > need the caching and abstraction properties. However, there are a few > other occurrences where efivar is not necessary, or used in an invalid > way. So let's fix this up, and remove some impediments to refactoring > and cleaning up the efivars layer in the future. > > Assuming there are no objections to these changes, I intend to queue > them up in the EFI tree fairly soon, so that ongoing work depending on > these changes can continue as well. > [...] > drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c | 25 ++--- > drivers/net/wireless/intel/iwlwifi/fw/uefi.c | 96 ++++++------------ Feel free to take the wireless patches via your tree: Acked-by: Kalle Valo <kvalo@xxxxxxxxxx> -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches