All of
 help / color / mirror / Atom feed
From: Randy Dunlap <>
Cc: Randy Dunlap <>,
	Matthew Wilcox <>,
	Andrew Morton <>
Subject: [PATCH] mm/workingset: correct kernel-doc notations
Date: Sun,  8 Aug 2021 13:31:53 -0700	[thread overview]
Message-ID: <> (raw)

Use the documented kernel-doc format to prevent kernel-doc warnings.

mm/workingset.c:256: warning: No description found for return value of 'workingset_eviction'
mm/workingset.c:285: warning: Function parameter or member 'folio' not described in 'workingset_refault'
mm/workingset.c:285: warning: Excess function parameter 'page' description in 'workingset_refault'

Signed-off-by: Randy Dunlap <>
Cc: Matthew Wilcox (Oracle) <>
Cc: Andrew Morton <>
 mm/workingset.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-next-20210806.orig/mm/workingset.c
+++ linux-next-20210806/mm/workingset.c
@@ -249,7 +249,7 @@ void workingset_age_nonresident(struct l
  * @target_memcg: the cgroup that is causing the reclaim
  * @page: the page being evicted
- * Returns a shadow entry to be stored in @page->mapping->i_pages in place
+ * Return: a shadow entry to be stored in @page->mapping->i_pages in place
  * of the evicted @page so that a later refault can be detected.
 void *workingset_eviction(struct page *page, struct mem_cgroup *target_memcg)
@@ -274,7 +274,7 @@ void *workingset_eviction(struct page *p
  * workingset_refault - evaluate the refault of a previously evicted folio
- * @page: the freshly allocated replacement folio
+ * @folio: the freshly allocated replacement folio
  * @shadow: shadow entry of the evicted folio
  * Calculates and evaluates the refault distance of the previously

                 reply	other threads:[~2021-08-08 20:31 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.