public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Marcin Jabrzyk <m.jabrzyk@samsung.com>
Cc: minchan@kernel.org, ngupta@vflare.org,
	linux-kernel@vger.kernel.org, sergey.senozhatsky.work@gmail.com,
	akpm@linux-foundation.org, kyungmin.park@samsung.com
Subject: Re: [PATCH] zram: remove obsolete ZRAM_DEBUG option
Date: Wed, 22 Apr 2015 08:55:52 +0900	[thread overview]
Message-ID: <20150421235552.GA1628@swordfish> (raw)
In-Reply-To: <1429615220-20676-1-git-send-email-m.jabrzyk@samsung.com>

On (04/21/15 13:20), Marcin Jabrzyk wrote:
> This config option doesn't provide any usage for zram.
> 

agree, there is no pr_debug() in the current zram. so the change
looks good to me.


btw, same stands for zsmalloc (for the time being):

 #ifdef CONFIG_ZSMALLOC_DEBUG
 #define DEBUG
 #endif

seems to be useless. and there is even no ZSMALLOC_DEBUG config option
in mm/Kconfig.

so let's return back to it and clean up after the merge window.

	-ss

> Signed-off-by: Marcin Jabrzyk <m.jabrzyk@samsung.com>
> ---
>  drivers/block/zram/Kconfig    | 10 +---------
>  drivers/block/zram/zram_drv.c |  4 ----
>  2 files changed, 1 insertion(+), 13 deletions(-)
> 
> diff --git a/drivers/block/zram/Kconfig b/drivers/block/zram/Kconfig
> index 6489c0fd0ea6..386ba3d1a6ee 100644
> --- a/drivers/block/zram/Kconfig
> +++ b/drivers/block/zram/Kconfig
> @@ -23,12 +23,4 @@ config ZRAM_LZ4_COMPRESS
>  	default n
>  	help
>  	  This option enables LZ4 compression algorithm support. Compression
> -	  algorithm can be changed using `comp_algorithm' device attribute.
> -
> -config ZRAM_DEBUG
> -	bool "Compressed RAM block device debug support"
> -	depends on ZRAM
> -	default n
> -	help
> -	  This option adds additional debugging code to the compressed
> -	  RAM block device driver.
> +	  algorithm can be changed using `comp_algorithm' device attribute.
> \ No newline at end of file
> diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> index fe67ebbe6c18..ea10f291d722 100644
> --- a/drivers/block/zram/zram_drv.c
> +++ b/drivers/block/zram/zram_drv.c
> @@ -15,10 +15,6 @@
>  #define KMSG_COMPONENT "zram"
>  #define pr_fmt(fmt) KMSG_COMPONENT ": " fmt
>  
> -#ifdef CONFIG_ZRAM_DEBUG
> -#define DEBUG
> -#endif
> -
>  #include <linux/module.h>
>  #include <linux/kernel.h>
>  #include <linux/bio.h>
> -- 
> 1.9.1
> 

  reply	other threads:[~2015-04-21 23:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 11:20 [PATCH] zram: remove obsolete ZRAM_DEBUG option Marcin Jabrzyk
2015-04-21 23:55 ` Sergey Senozhatsky [this message]
2015-04-22  6:39   ` Marcin Jabrzyk
2015-04-22  7:02     ` Sergey Senozhatsky
2015-04-22  8:52 ` [PATCH v2 0/2] zram, zsmalloc: remove obsolete DEBUGs Marcin Jabrzyk
2015-04-22  8:52   ` [PATCH v2 1/2] zram: remove obsolete ZRAM_DEBUG option Marcin Jabrzyk
2015-04-22  8:52   ` [PATCH v2 2/2] zsmalloc: remove obsolete ZSMALLOC_DEBUG Marcin Jabrzyk
2015-04-22  9:18   ` [PATCH v2 0/2] zram, zsmalloc: remove obsolete DEBUGs Sergey Senozhatsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150421235552.GA1628@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.jabrzyk@samsung.com \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox