From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, kernel-team@meta.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH mm-unstable 2/2] mm/damon: remove damon_ctx->callback kernel-doc comment
Date: Tue, 15 Jul 2025 11:52:39 -0700 [thread overview]
Message-ID: <20250715185239.89152-3-sj@kernel.org> (raw)
In-Reply-To: <20250715185239.89152-1-sj@kernel.org>
Commit 769bd386e490 ("mm/damon/core: add cleanup_target() ops callback")
on mm-unstable tree removed callback field of damon_ctx, but not erased
the kernel-doc comment for the field. This results in build warning.
Fix it by removing the obsolete comment.
Fixes: 769bd386e490 ("mm/damon/core: add cleanup_target() ops callback")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Fixes: 769bd386e490 ("mm/damon/core: add cleanup_target() ops callback") # mm-unstable
Signed-off-by: SeongJae Park <sj@kernel.org>
---
include/linux/damon.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/damon.h b/include/linux/damon.h
index efabc3ba52ee..f13664c62ddd 100644
--- a/include/linux/damon.h
+++ b/include/linux/damon.h
@@ -746,7 +746,6 @@ struct damon_attrs {
* Accesses to other fields must be protected by themselves.
*
* @ops: Set of monitoring operations for given use cases.
- * @callback: Set of callbacks for monitoring events notifications.
*
* @adaptive_targets: Head of monitoring targets (&damon_target) list.
* @schemes: Head of schemes (&damos) list.
--
2.39.5
prev parent reply other threads:[~2025-07-15 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 18:52 [PATCH mm-unstable 0/2] mm/damon: kernel-doc comments fixup for damon_callback removal SeongJae Park
2025-07-15 18:52 ` [PATCH mm-unstable 1/2] mm/damon: add kernel-doc comment for damon_operations->cleanup_target SeongJae Park
2025-07-15 18:52 ` SeongJae Park [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=20250715185239.89152-3-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®