summaryrefslogtreecommitdiffstats
path: root/init/version.c
diff options
context:
space:
mode:
authorLuis R. Rodriguez <mcgrof@kernel.org>2018-03-10 06:14:56 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-03-20 09:28:47 +0100
commitd15d7311550983be97dca44ad68cbc2ca001297b (patch)
tree77ce8db70dd8e6155c23da4b335959e05374ab76 /init/version.c
parent60fa74263cbeae1704908c403aba2bfd62c798e8 (diff)
downloadlinux-stable-d15d7311550983be97dca44ad68cbc2ca001297b.tar.gz
linux-stable-d15d7311550983be97dca44ad68cbc2ca001297b.tar.bz2
linux-stable-d15d7311550983be97dca44ad68cbc2ca001297b.zip
firmware: fix checking for return values for fw_add_devm_name()
Currently fw_add_devm_name() returns 1 if the firmware cache was already set. This makes it complicated for us to check for correctness. It is actually non-fatal if the firmware cache is already setup, so just return 0, and simplify the checkers. fw_add_devm_name() adds device's name onto the devres for the device so that prior to suspend we cache the firmware onto memory, so that on resume the firmware is reliably available. We never were checking for success for this call though, meaning in some really rare cases we my have never setup the firmware cache for a device, which could in turn make resume fail. This is all theoretical, no known issues have been reported. This small issue has been present way since the addition of the devres firmware cache names on v3.7. Fixes: f531f05ae9437 ("firmware loader: store firmware name into devres list") Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'init/version.c')
0 files changed, 0 insertions, 0 deletions