Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   yongw.pur@gmail.com
To:     minchan@kernel.org, ngupta@vflare.org, senozhatsky@chromium.org,
        axboe@kernel.dk, linux-kernel@vger.kernel.org,
        linux-block@vger.kernel.org, wang.yong12@zte.com.cn
Subject: [PATCH] zram: zcomp_strm remove ambiguous description
Date:   Mon,  7 Jun 2021 09:08:20 -0700
Message-Id: <1623082100-22086-1-git-send-email-yongw.pur@gmail.com>
Precedence: bulk

From: wangyong <wang.yong12@zte.com.cn>

buffer element in the structure is only used for compression.
buffer element is not used in decompression.
So "/* compression/decompression buffer */" is a little ambiguous.

buffer is used in the following two places:
1.__zram_bvec_write: src = zstrm->buffer
2.zcomp_compress: crypto_comp_compress(zstrm->tfm,
                        src, PAGE_SIZE,
                        zstrm->buffer, dst_len);

Signed-off-by: wangyong <wang.yong12@zte.com.cn>
---
 drivers/block/zram/zcomp.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/block/zram/zcomp.h b/drivers/block/zram/zcomp.h
index 40f6420..0aac4b2 100644
--- a/drivers/block/zram/zcomp.h
+++ b/drivers/block/zram/zcomp.h
@@ -10,7 +10,7 @@
 struct zcomp_strm {
 	/* The members ->buffer and ->tfm are protected by ->lock. */
 	local_lock_t lock;
-	/* compression/decompression buffer */
+	/* compression buffer */
 	void *buffer;
 	struct crypto_comp *tfm;
 };
-- 
2.7.4