diff options
| author | Masahiro Yamada <masahiroy@kernel.org> | 2022-01-10 03:15:26 +0900 |
|---|---|---|
| committer | Masahiro Yamada <masahiroy@kernel.org> | 2022-01-14 02:52:04 +0900 |
| commit | 64d8aaa4ef388b22372de4dc9ce3b9b3e5f45b6c (patch) | |
| tree | c11e5f53721e916bc4a3265adc80f045fee6b98d /usr | |
| parent | 82977af93a0dc4e70f60ca2137b67f65ebe47fc7 (diff) | |
| download | linux-stable-64d8aaa4ef388b22372de4dc9ce3b9b3e5f45b6c.tar.gz linux-stable-64d8aaa4ef388b22372de4dc9ce3b9b3e5f45b6c.tar.bz2 linux-stable-64d8aaa4ef388b22372de4dc9ce3b9b3e5f45b6c.zip | |
kbuild: drop $(size_append) from cmd_zstd
The appended file size is only used by the decompressors, which some
architectures support.
As the comment "zstd22 is used for kernel compression" says, cmd_zstd22
is used in arch/{mips,s390,x86}/boot/compressed/Makefile.
On the other hand, there is no good reason to append the file size to
cmd_zstd since it is used for other purposes.
Actually cmd_zstd is only used in usr/Makefile, where the appended file
size is rather harmful.
The initramfs with its file size appended is considered as corrupted
data, so commit 65e00e04e5ae ("initramfs: refactor the initramfs build
rules") added 'override size_append := :' to make it no-op.
As a conclusion, this $(size_append) should not exist here.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Nicolas Schier <n.schier@avm.de>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions