mirror of
https://github.com/edk2-porting/linux-next.git
synced 2025-01-01 18:24:23 +08:00
d68772b7c8
Now that efivarfs uses the efivar API, move it out of efivars.c and
into fs/efivarfs where it belongs. This move will eventually allow us
to enable the efivarfs code without having to also enable
CONFIG_EFI_VARS built, and vice versa.
Furthermore, things like,
mount -t efivarfs none /sys/firmware/efi/efivars
will now work if efivarfs is built as a module without requiring the
use of MODULE_ALIAS(), which would have been necessary when the
efivarfs code was part of efivars.c.
Cc: Matthew Garrett <matthew.garrett@nebula.com>
Cc: Jeremy Kerr <jk@ozlabs.org>
Reviewed-by: Tom Gundersen <teg@jklm.no>
Tested-by: Tom Gundersen <teg@jklm.no>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
13 lines
365 B
Plaintext
13 lines
365 B
Plaintext
config EFIVAR_FS
|
|
tristate "EFI Variable filesystem"
|
|
depends on EFI_VARS
|
|
help
|
|
efivarfs is a replacement filesystem for the old EFI
|
|
variable support via sysfs, as it doesn't suffer from the
|
|
same 1024-byte variable size limit.
|
|
|
|
To compile this file system support as a module, choose M
|
|
here. The module will be called efivarfs.
|
|
|
|
If unsure, say N.
|