- May 31, 2022
-
-
Konrad Weihmann authored
mkdir -p creates paths that are bound to user's settings and therefore can lead to different file mode bits of the base paths accross different machines. Use install instead, as this tool is not prone to such behavior. Signed-off-by:
Konrad Weihmann <kweihmann@outlook.com> Signed-off-by:
Josh Boyer <jwboyer@kernel.org>
-
- Oct 05, 2020
-
-
Tony Nguyen authored
File: entries in the WHENCE file overwrite existing files in the target directory, however, Link: entries are skipped if the file exists in the target directory. This can cause issues if the Link: entry is updated, but the target directory contains an old symlink. Do not skip writing Link: entries if the file exists, always create the symlink. This matches the behavior of File: entries and ensures symlinks will contain values from the WHENCE file. Signed-off-by:
Tony Nguyen <anthony.l.nguyen@intel.com> Signed-off-by:
Josh Boyer <jwboyer@kernel.org>
-
- Oct 04, 2019
-
-
Thierry Reding authored
Rather than require symlinks to be created in the filesystem and have duplicate Link: entries in the WHENCE file, make copy-firmware.sh create the symlinks on the fly. Signed-off-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Josh Boyer <jwboyer@kernel.org>
-
- Aug 15, 2019
-
-
Takashi Iwai authored
The current make-install procedure leaves lots of garbage files that aren't really firmware files in /lib/firmware. Instead of copy-all-and-prune approach, copy only the listed files and links in WHENCE by make-install for assuring only the proper firmware files. Signed-off-by:
Takashi Iwai <tiwai@suse.de> Signed-off-by:
Josh Boyer <jwboyer@kernel.org>
-