From: Minchan Kim <minchan@kernel.org>
To: yang.yang29@zte.com.cn
Cc: ngupta@vflare.org, senozhatsky@chromium.org, axboe@kernel.dk,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
xu.panda@zte.com.cn
Subject: Re: [PATCH linux-next v2] zram: use sysfs_emit() to instead of scnprintf()
Date: Tue, 15 Nov 2022 15:32:46 -0800 [thread overview]
Message-ID: <Y3QhnpQQ/y58XyVh@google.com> (raw)
In-Reply-To: <202211152004478289568@zte.com.cn>
Hi,
On Tue, Nov 15, 2022 at 08:04:47PM +0800, yang.yang29@zte.com.cn wrote:
> From: Xu Panda <xu.panda@zte.com.cn>
>
> Replace the open-code with sysfs_emit() to simplify the code.
> ---
> change for v2
> - realign params of sysfs_emit().
> ---
>
> Signed-off-by: Xu Panda <xu.panda@zte.com.cn>
> Signed-off-by: Yang Yang <yang.yang29@zte.com>
Recently, we added one more stat is using the scnprintf in mm-unstable
tree? recomp_algorithm_show
Could you also change it?
Thanks!
prev parent reply other threads:[~2022-11-15 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 12:04 [PATCH linux-next v2] zram: use sysfs_emit() to instead of scnprintf() yang.yang29
2022-11-15 23:32 ` 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=Y3QhnpQQ/y58XyVh@google.com \
--to=minchan@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.org \
--cc=xu.panda@zte.com.cn \
--cc=yang.yang29@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).