From: sashiko-bot@kernel.org
To: "SeongJae Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH 1/2] Docs/admin-guide/mm/damon/usage: mark scheme filters sysfs dir as deprecated
Date: Tue, 21 Apr 2026 05:04:13 +0000 [thread overview]
Message-ID: <20260421050414.6B856C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260421044928.141388-2-sj@kernel.org>
Sashiko AI review found 1 potential issue(s):
- [Low] Poor grammar and inappropriate terminology in the deprecation notice.
--
commit bd6da1d76d24f1b76f6957dd9993c899af48df43
Author: SeongJae Park <sj@kernel.org>
Docs/admin-guide/mm/damon/usage: mark scheme filters sysfs dir as deprecated
This commit updates the DAMON usage documentation to formally mark the
sysfs 'filters/' directory as deprecated. It recommends users migrate
to the 'core_filters/' and 'ops_filters/' directories instead.
> diff --git a/Documentation/admin-guide/mm/damon/usage.rst b/Documentation/admin-guide/mm/damon/usage.rst
> index 534e1199cf091..4c222e956b100 100644
> --- a/Documentation/admin-guide/mm/damon/usage.rst
> +++ b/Documentation/admin-guide/mm/damon/usage.rst
[ ... ]
> Use of ``filters`` directory can make expecting evaluation orders of given
> -filters with the files under directory bit confusing. Users are hence
> -recommended to use ``core_filters`` and ``ops_filters`` directories. The
> -``filters`` directory could be deprecated in future.
> +filters with the files under directory bit confusing. For the reason,
> +``filters`` directory is deprecated. It is still functioning, but it will be
> +broken and eventually removed in near future. Users should use
> +``core_filters`` and ``ops_filters`` directories instead.
This isn't a bug, but could the phrasing here be smoothed out a bit? There
are a few awkward phrases like "make expecting evaluation orders" and "with
the files under directory bit confusing".
Also, stating that a sysfs interface "will be broken" is generally avoided
in kernel documentation. The standard convention is to say that an interface
is "deprecated and scheduled for removal" to avoid implying that userspace
will be intentionally broken.
Would a rewrite like this work better?
"Using the ``filters`` directory can make the evaluation order of filters
confusing. For this reason, the ``filters`` directory is deprecated. It
continues to function for now, but is scheduled for removal in the near
future."
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260421044928.141388-1-sj@kernel.org?part=1
next prev parent reply other threads:[~2026-04-21 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 4:49 [RFC PATCH 0/2] mm/damon/sysfs: document filters/ directory as deprecated SeongJae Park
2026-04-21 4:49 ` [RFC PATCH 1/2] Docs/admin-guide/mm/damon/usage: mark scheme filters sysfs dir " SeongJae Park
2026-04-21 5:04 ` sashiko-bot [this message]
2026-04-21 5:29 ` SeongJae Park
2026-04-21 4:49 ` [RFC PATCH 2/2] Docs/ABI/damon: mark schemes/<S>/filters/ deprecated SeongJae Park
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=20260421050414.6B856C2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko@lists.linux.dev \
--cc=sj@kernel.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