linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <1623082100-22086-1-git-send-email-yongw.pur@gmail.com> (raw)

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


                 reply	other threads:[~2021-06-07 16:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1623082100-22086-1-git-send-email-yongw.pur@gmail.com \
    --to=yongw.pur@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=senozhatsky@chromium.org \
    --cc=wang.yong12@zte.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).