summaryrefslogtreecommitdiff
path: root/drivers/firmware
diff options
context:
space:
mode:
authorJohannes Thumshirn <jthumshirn@suse.de>2018-02-09 16:20:45 +0300
committerJiri Kosina <jkosina@suse.cz>2018-03-27 10:51:23 +0300
commitbade9835a22e03a00d6cb94350984620bf808f83 (patch)
tree71ee33bb4c6a53084260a317e32bfeefc69971c5 /drivers/firmware
parent1897a9691e384f6e30b8e8e30fc75d00e402e0ca (diff)
downloadlinux-bade9835a22e03a00d6cb94350984620bf808f83.tar.xz
edd: don't spam log if no EDD information is present
We've had reports from users being concerned about messages like: [ 4.487246] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 4.487251] EDD information not available. While these are more or less irrelevant, tell edd.c to not annoy anyone. Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/firmware')
-rw-r--r--drivers/firmware/edd.c8
1 files changed, 3 insertions, 5 deletions
diff --git a/drivers/firmware/edd.c b/drivers/firmware/edd.c
index 60a8f1363a10..1b82c89a49df 100644
--- a/drivers/firmware/edd.c
+++ b/drivers/firmware/edd.c
@@ -748,14 +748,12 @@ edd_init(void)
int rc=0;
struct edd_device *edev;
+ if (!edd_num_devices())
+ return -ENODEV;
+
printk(KERN_INFO "BIOS EDD facility v%s %s, %d devices found\n",
EDD_VERSION, EDD_DATE, edd_num_devices());
- if (!edd_num_devices()) {
- printk(KERN_INFO "EDD information not available.\n");
- return -ENODEV;
- }
-
edd_kset = kset_create_and_add("edd", NULL, firmware_kobj);
if (!edd_kset)
return -ENOMEM;