Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758231Ab2J2IvY (ORCPT ); Mon, 29 Oct 2012 04:51:24 -0400 Received: from LGEMRELSE7Q.lge.com ([156.147.1.151]:55060 "EHLO LGEMRELSE7Q.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758120Ab2J2IvU (ORCPT ); Mon, 29 Oct 2012 04:51:20 -0400 X-AuditID: 9c930197-b7c4aae000004160-25-508e437ab2c4 From: Minchan Kim To: Greg Kroah-Hartman Cc: Andrew Morton , Nitin Gupta , Konrad Rzeszutek Wilk , Seth Jennings , Jens Axboe , Dan Magenheimer , Pekka Enberg , gaowanlong@cn.fujitsu.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Minchan Kim Subject: [PATCH v3 3/3] zram: select ZSMALLOC when ZRAM is configured Date: Mon, 29 Oct 2012 17:56:49 +0900 Message-Id: <1351501009-15111-4-git-send-email-minchan@kernel.org> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <1351501009-15111-1-git-send-email-minchan@kernel.org> References: <1351501009-15111-1-git-send-email-minchan@kernel.org> X-Brightmail-Tracker: AAAAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 998 Lines: 32 At the monent, we can configure zram in driver/block once zsmalloc in /lib menu is configured firstly. It's not convenient. User can configure zram in driver/block regardless of zsmalloc enabling by this patch. Signed-off-by: Minchan Kim --- drivers/block/zram/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/block/zram/Kconfig b/drivers/block/zram/Kconfig index be5abe8..ee23a86 100644 --- a/drivers/block/zram/Kconfig +++ b/drivers/block/zram/Kconfig @@ -1,6 +1,7 @@ config ZRAM tristate "Compressed RAM block device support" - depends on BLOCK && SYSFS && ZSMALLOC + depends on BLOCK && SYSFS + select ZSMALLOC select LZO_COMPRESS select LZO_DECOMPRESS default n -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/