From: JeongHyeon Lee <jhs2.lee@samsung.com>
To: minchan@kernel.org
Cc: ngupta@vflare.org, senozhatsky@chromium.org, axboe@kernel.dk,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
JeongHyeon Lee <jhs2.lee@samsung.com>
Subject: [PATCH] zram: fix typos in comments
Date: Tue, 2 Aug 2022 17:41:34 +0900 [thread overview]
Message-ID: <20220802084134.27202-1-jhs2.lee@samsung.com> (raw)
In-Reply-To: <CGME20220802084138epcas1p22d18382ac9a3ae0990c53e0273645755@epcas1p2.samsung.com>
- The double `range` is duplicated in comment, remove one.
- change `syfs` to `sysfs`
Signed-off-by: JeongHyeon Lee <jhs2.lee@samsung.com>
---
drivers/block/zram/zram_drv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
index b8549c61ff2c..dc91d7587bbb 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -172,7 +172,7 @@ static inline bool valid_io_request(struct zram *zram,
end = start + (size >> SECTOR_SHIFT);
bound = zram->disksize >> SECTOR_SHIFT;
- /* out of range range */
+ /* out of range */
if (unlikely(start >= bound || end > bound || start > end))
return false;
@@ -1917,7 +1917,7 @@ static int zram_add(void)
zram->disk->private_data = zram;
snprintf(zram->disk->disk_name, 16, "zram%d", device_id);
- /* Actual capacity set using syfs (/sys/block/zram<id>/disksize */
+ /* Actual capacity set using sysfs (/sys/block/zram<id>/disksize */
set_capacity(zram->disk, 0);
/* zram devices sort of resembles non-rotational disks */
blk_queue_flag_set(QUEUE_FLAG_NONROT, zram->disk->queue);
--
2.34.1
next parent reply other threads:[~2022-08-02 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220802084138epcas1p22d18382ac9a3ae0990c53e0273645755@epcas1p2.samsung.com>
2022-08-02 8:41 ` JeongHyeon Lee [this message]
[not found] <CGME20221223040335epcas1p45bda0013a3a42f176fa137e0597fd7c9@epcas1p4.samsung.com>
2022-12-23 4:03 ` JeongHyeon Lee
2022-12-23 11:51 ` 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=20220802084134.27202-1-jhs2.lee@samsung.com \
--to=jhs2.lee@samsung.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 \
/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
all inboxes | Powered by JetHome®