From nobody Sun Nov 24 11:53:01 2024 Received: from laurent.telenet-ops.be (laurent.telenet-ops.be [195.130.137.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D810F1D3593 for ; Tue, 5 Nov 2024 11:50:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=195.130.137.89 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730807446; cv=none; b=NWnYwFda2CDAqJhv6NDdylXYYF/8BhPvluPQ4J0nS6YoKrbGgJqUbV3/FDjNmnKaDtANug0Bd1hEUeam9s53taVUxcwUmaqTxky2Rg3KAdsJYJAA6BPCG1UKM62G6DaFaFvZ2q/a+FEnNKocKd4h5Ho33xcWGkLgQKGp+Lz2OIg= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730807446; c=relaxed/simple; bh=eFmDTZ0mvH40C2n3riuUszzKOF00psDdI40q8+QQoxM=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=LN0E8XUvYaZUBNBpea8fQVaOAwUL8eRBgY5oNTcxmwy4aoBk8CozR3iBk31wy3pBU9nG1S1gP/bYWVzYa76W9xcbSnwjs2u/HlDEqqx747ST+RchJEZZ6g7EfNBe3hz1rR/b3qgfGCVOmltE3z23D3Q6dC7vVVbputnjYyjHXLY= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org; spf=none smtp.mailfrom=linux-m68k.org; arc=none smtp.client-ip=195.130.137.89 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux-m68k.org Received: from ramsan.of.borg ([IPv6:2a02:1810:ac12:ed80:ae0d:26ef:36dd:9be1]) by laurent.telenet-ops.be with cmsmtp id Yzqd2D00131l0Qj01zqdxS; Tue, 05 Nov 2024 12:50:37 +0100 Received: from rox.of.borg ([192.168.97.57]) by ramsan.of.borg with esmtp (Exim 4.95) (envelope-from ) id 1t8I4f-006J5k-7r; Tue, 05 Nov 2024 12:50:37 +0100 Received: from geert by rox.of.borg with local (Exim 4.95) (envelope-from ) id 1t8I4y-000nlT-Rz; Tue, 05 Nov 2024 12:50:36 +0100 From: Geert Uytterhoeven To: Minchan Kim , Sergey Senozhatsky , Jens Axboe , Andrew Morton Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven Subject: [PATCH] zram: ZRAM_DEF_COMP should depend on ZRAM Date: Tue, 5 Nov 2024 12:50:35 +0100 Message-Id: <64e05bad68a9bd5cc322efd114a04d25de525940.1730807319.git.geert@linux-m68k.org> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" When Compressed RAM block device support is disabled, the CONFIG_ZRAM_DEF_COMP symbol still ends up in the generated config file: CONFIG_ZRAM_DEF_COMP=3D"unset-value" While this causes no real harm, avoid polluting the config file by adding a dependency on ZRAM. Fixes: 917a59e81c342f47 ("zram: introduce custom comp backends API") Signed-off-by: Geert Uytterhoeven Reviewed-by: Sergey Senozhatsky --- drivers/block/zram/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/block/zram/Kconfig b/drivers/block/zram/Kconfig index 6aea609b795c2f36..402b7b1758632807 100644 --- a/drivers/block/zram/Kconfig +++ b/drivers/block/zram/Kconfig @@ -94,6 +94,7 @@ endchoice =20 config ZRAM_DEF_COMP string + depends on ZRAM default "lzo-rle" if ZRAM_DEF_COMP_LZORLE default "lzo" if ZRAM_DEF_COMP_LZO default "lz4" if ZRAM_DEF_COMP_LZ4 --=20 2.34.1