From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
<zhouxianrong@huawei.com>, <linux-kernel@vger.kernel.org>,
<sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] zram: remove obsolete sysfs attrs
Date: Mon, 23 Jan 2017 15:04:08 +0900 [thread overview]
Message-ID: <20170123060408.GB12327@bbox> (raw)
In-Reply-To: <20170118035838.11090-1-sergey.senozhatsky@gmail.com>
On Wed, Jan 18, 2017 at 12:58:38PM +0900, Sergey Senozhatsky wrote:
> We had a deprecated_attr_warn() warning for 2 years and now the
> time has come and we finally can do the cleanup.
>
> The plan was as follows:
>
> : per-stat sysfs attributes are considered to be deprecated.
> : The basic strategy is:
> : -- the existing RW nodes will be downgraded to WO nodes (in linux 4.11)
> : -- deprecated RO sysfs nodes will eventually be removed (in linux 4.11)
> :
> : The list of deprecated attributes can be found here:
> : Documentation/ABI/obsolete/sysfs-block-zram
> :
> : Basically, every attribute that has its own read accessible sysfs
> : node (e.g. num_reads) *AND* is accessible via one of the stat files
> : (zram<id>/stat or zram<id>/io_stat or zram<id>/mm_stat) is considered
> : to be deprecated.
>
> The patch also removes `obsolete/sysfs-block-zram', clean ups
> `testing/sysfs-block-zram' and tweaks zram.txt files.
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Acked-by: Minchan Kim <minchan@kernel.org>
next prev parent reply other threads:[~2017-01-23 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 3:58 [PATCH] zram: remove obsolete sysfs attrs Sergey Senozhatsky
2017-01-18 4:01 ` Sergey Senozhatsky
2017-01-23 6:04 ` Minchan Kim [this message]
2017-01-23 6:20 ` 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=20170123060408.GB12327@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=zhouxianrong@huawei.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