From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, rostedt@goodmis.org, corbet@lwn.net,
sj@kernel.org, akpm@linux-foundation.org
Subject: [merged mm-stable] mm-damon-core-remove-duplicated-comment-for-watermarks-based-deactivation.patch removed from -mm tree
Date: Wed, 04 Oct 2023 13:18:41 -0700 [thread overview]
Message-ID: <20231004201843.4A147C433C7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/damon/core: remove duplicated comment for watermarks-based deactivation
has been removed from the -mm tree. Its filename was
mm-damon-core-remove-duplicated-comment-for-watermarks-based-deactivation.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: SeongJae Park <sj@kernel.org>
Subject: mm/damon/core: remove duplicated comment for watermarks-based deactivation
Date: Thu, 7 Sep 2023 02:29:28 +0000
The comment for explaining about watermarks-based monitoring part
deactivation is duplicated in two paragraphs. Remove one.
Link: https://lkml.kernel.org/r/20230907022929.91361-11-sj@kernel.org
Signed-off-by: SeongJae Park <sj@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/damon.h | 3 ---
1 file changed, 3 deletions(-)
--- a/include/linux/damon.h~mm-damon-core-remove-duplicated-comment-for-watermarks-based-deactivation
+++ a/include/linux/damon.h
@@ -317,9 +317,6 @@ struct damos_access_pattern {
* monitoring context are inactive, DAMON stops monitoring either, and just
* repeatedly checks the watermarks.
*
- * If all schemes that registered to a &struct damon_ctx are inactive, DAMON
- * stops monitoring and just repeatedly checks the watermarks.
- *
* Before applying the &action to a memory region, &struct damon_operations
* implementation could check pages of the region and skip &action to respect
* &filters
_
Patches currently in -mm which might be from sj@kernel.org are
reply other threads:[~2023-10-04 20:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231004201843.4A147C433C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.