diff options
| author | Florian Fainelli <f.fainelli@gmail.com> | 2023-04-13 12:17:57 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-04-20 11:42:27 +0200 |
| commit | 495ff36388e8b71eb49e9242c8e04e06c5609e74 (patch) | |
| tree | 506cf451a1d0aa6e66e10d520d214e5a275340e3 /drivers/platform/x86/intel/pmt/class.c | |
| parent | a7b3a470fdea9f4a7daa5ae446c4e27c65f00aac (diff) | |
| download | linux-495ff36388e8b71eb49e9242c8e04e06c5609e74.tar.gz linux-495ff36388e8b71eb49e9242c8e04e06c5609e74.tar.bz2 linux-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/20230402135423.3235-1-f.fainelli@gmail.com/
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Link: https://lore.kernel.org/r/20230413191757.1949088-1-f.fainelli@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/platform/x86/intel/pmt/class.c')
0 files changed, 0 insertions, 0 deletions