aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/fpga/fpga-bridge.c
diff options
context:
space:
mode:
authorFlorian Fainelli <[email protected]>2023-04-13 19:17:57 +0000
committerGreg Kroah-Hartman <[email protected]>2023-04-20 09:42:27 +0000
commit495ff36388e8b71eb49e9242c8e04e06c5609e74 (patch)
tree506cf451a1d0aa6e66e10d520d214e5a275340e3 /drivers/fpga/fpga-bridge.c
parentMerge tag 'cacheinfo-updates-6.4' of git://git.kernel.org/pub/scm/linux/kerne... (diff)
downloadkernel-495ff36388e8b71eb49e9242c8e04e06c5609e74.tar.gz
kernel-495ff36388e8b71eb49e9242c8e04e06c5609e74.zip
firmware_loader: Strip off \n from customized path
Having helped an user recently figure out why the customized path being specified was not taken into account landed on a subtle difference between using: echo "/xyz/firmware" > /sys/module/firmware_class/parameters/path which inserts an additional newline which is passed as is down to fw_get_filesystem_firmware() and ultimately kernel_read_file_from_path() and fails. Strip off \n from the customized firmware path such that users do not run into these hard to debug situations. Link: https://lore.kernel.org/all/[email protected]/ Signed-off-by: Florian Fainelli <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'drivers/fpga/fpga-bridge.c')
0 files changed, 0 insertions, 0 deletions