From: Minchan Kim <minchan@kernel.org>
To: Yue Hu <zbestahu@gmail.com>
Cc: ngupta@vflare.org, sergey.senozhatsky.work@gmail.com,
linux-kernel@vger.kernel.org, huyue2@yulong.com
Subject: Re: [PATCH] zram: move backing_dev under macro CONFIG_ZRAM_WRITEBACK
Date: Wed, 22 Jan 2020 17:54:29 -0800 [thread overview]
Message-ID: <20200123015429.GD249784@google.com> (raw)
In-Reply-To: <20200120034155.6048-1-zbestahu@gmail.com>
On Mon, Jan 20, 2020 at 11:41:55AM +0800, Yue Hu wrote:
> From: Yue Hu <huyue2@yulong.com>
>
> backing_dev is never used when not enable CONFIG_ZRAM_WRITEBACK and
> it's introduced from writeback feature. So it's needless also affect
> readability in that case.
>
> Signed-off-by: Yue Hu <huyue2@yulong.com>
Acked-by: Minchan Kim <minchan@kernel.org>
prev parent reply other threads:[~2020-01-23 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 3:41 [PATCH] zram: move backing_dev under macro CONFIG_ZRAM_WRITEBACK Yue Hu
2020-01-20 5:30 ` Sergey Senozhatsky
2020-01-23 1:54 ` Minchan Kim [this message]
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=20200123015429.GD249784@google.com \
--to=minchan@kernel.org \
--cc=huyue2@yulong.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=zbestahu@gmail.com \
/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