linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Khalid Masum <khalid.masum.92@gmail.com>
To: linux-kernel-mentees@lists.linuxfoundation.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	SeongJae Park <sj@kernel.org>
Cc: damon@lists.linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	Khalid Masum <khalid.masum.92@gmail.com>
Subject: [PATCH] mm/daemon: describe NR_DAMON_OPS in damon_ops_id
Date: Tue, 24 May 2022 02:53:36 +0600	[thread overview]
Message-ID: <20220523205336.2435-1-khalid.masum.92@gmail.com> (raw)

NR_DAMON_OPS in the enum damon_ops_id is not described. Describe it for
better readability and also to fix a warning generated by make docs.

"NR" is described as "Total Number" and "DAMON_OPS" is described as
"Monitoring operations" in the same file. Hence describe NR_DAMON_OPS
as "Total number of damon operations".

Signed-off-by: Khalid Masum <khalid.masum.92@gmail.com>
---
 include/linux/damon.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/linux/damon.h b/include/linux/damon.h
index f23cbfa42..9e9fb4d78 100644
--- a/include/linux/damon.h
+++ b/include/linux/damon.h
@@ -262,6 +262,7 @@ struct damos {
  *
  * @DAMON_OPS_VADDR:	Monitoring operations for virtual address spaces
  * @DAMON_OPS_PADDR:	Monitoring operations for the physical address space
+ * @NR_DAMON_OPS:	Total number of monitoring operations
  */
 enum damon_ops_id {
 	DAMON_OPS_VADDR,
-- 
2.25.1



             reply	other threads:[~2022-05-23 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 20:53 Khalid Masum [this message]
2022-05-23 21:12 ` [PATCH] mm/daemon: describe NR_DAMON_OPS in damon_ops_id 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=20220523205336.2435-1-khalid.masum.92@gmail.com \
    --to=khalid.masum.92@gmail.com \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sj@kernel.org \
    --cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).