summaryrefslogtreecommitdiff
path: root/security/keys
diff options
context:
space:
mode:
authorArd Biesheuvel <ard.biesheuvel@linaro.org>2018-02-03 11:25:20 +0100
committerJean Delvare <jdelvare@suse.de>2018-02-03 11:25:20 +0100
commita81114d03e4a529c4b68293249f75438b3c1783f (patch)
tree0a15235314cb80327f135e18d4eb8786062122c8 /security/keys
parenta7770ae194569e96a93c48aceb304edded9cc648 (diff)
firmware: dmi: handle missing DMI data gracefully
Currently, when booting a kernel with DMI support on a platform that has no DMI tables, the following output is emitted into the kernel log: [ 0.128818] DMI not present or invalid. ... [ 1.306659] dmi: Firmware registration failed. ... [ 2.908681] dmi-sysfs: dmi entry is absent. The first one is a pr_info(), but the subsequent ones are pr_err()s that complain about a condition that is not really an error to begin with. So let's clean this up, and give up silently if dma_available is not set. Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Acked-by: Martin Hundebøll <mnhu@prevas.dk> Signed-off-by: Jean Delvare <jdelvare@suse.de>
Diffstat (limited to 'security/keys')
0 files changed, 0 insertions, 0 deletions