summaryrefslogtreecommitdiffstats
path: root/drivers/firmware
diff options
context:
space:
mode:
authorMatt Fleming <matt.fleming@intel.com>2014-01-15 13:36:33 +0000
committerMatt Fleming <matt.fleming@intel.com>2014-03-04 16:16:16 +0000
commit0f8093a92da77afe24fd258a5a1037bb2b97a870 (patch)
treeacd0f1a2db891fb906e33014fc5356f0f4c80acd /drivers/firmware
parent3e909599215456928e6b42a04f11c2517881570b (diff)
downloadlinux-0f8093a92da77afe24fd258a5a1037bb2b97a870.tar.bz2
efi: Set feature flags inside feature init functions
It makes more sense to set the feature flag in the success path of the detection function than it does to rely on the caller doing it. Apart from it being more logical to group the code and data together, it sets a much better example for new EFI architectures. Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Diffstat (limited to 'drivers/firmware')
-rw-r--r--drivers/firmware/efi/efi.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
index 4753bac65279..b25b36b1ef23 100644
--- a/drivers/firmware/efi/efi.c
+++ b/drivers/firmware/efi/efi.c
@@ -313,5 +313,8 @@ int __init efi_config_init(efi_config_table_type_t *arch_tables)
}
pr_cont("\n");
early_iounmap(config_tables, efi.systab->nr_tables * sz);
+
+ set_bit(EFI_CONFIG_TABLES, &efi.flags);
+
return 0;
}