public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Andrew Morton <akpm@linux-foundation•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the mm-unstable tree
Date: Fri, 11 Jul 2025 11:57:37 +0200	[thread overview]
Message-ID: <d96e2916-2c43-462c-b6a1-2375ef397d8b@redhat.com> (raw)
In-Reply-To: <20250710175020.6efdcc8f@canb.auug.org.au>

On 10.07.25 09:50, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the mm-unstable tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> include/linux/page-flags.h:1161: warning: Function parameter or struct member 'page' not described in 'page_has_movable_ops'
> 
> Introduced by commit
> 
>    7a93faa2375d ("mm: convert "movable" flag in page->mapping to a page flag")
> 

Ah, there is a ":" missing.

diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
index 970600d79daca..8e4d6eda8a8d6 100644
--- a/include/linux/page-flags.h
+++ b/include/linux/page-flags.h
@@ -1150,7 +1150,7 @@ PAGEFLAG_FALSE(MovableOpsIsolated, 
movable_ops_isolated);

  /**
   * page_has_movable_ops - test for a movable_ops page
- * @page The page to test.
+ * @page: The page to test.
   *
   * Test whether this is a movable_ops page. Such pages will stay that
   * way until freed.


-- 
Cheers,

David / dhildenb


  reply	other threads:[~2025-07-11  9:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10  7:50 linux-next: build warning after merge of the mm-unstable tree Stephen Rothwell
2025-07-11  9:57 ` David Hildenbrand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-07  3:39 Stephen Rothwell
2025-11-07  6:51 ` Randy Dunlap
2025-10-20  2:49 Stephen Rothwell
2025-10-20  2:45 Stephen Rothwell
2025-10-20  3:41 ` Baoquan He
2025-10-20  4:19   ` Bagas Sanjaya
2025-09-12  4:12 Stephen Rothwell
2025-09-12  4:58 ` Balbir Singh
2025-09-04  2:14 Stephen Rothwell
2025-09-04  2:59 ` Andrew Morton
2025-09-04  6:33   ` David Hildenbrand
2025-07-15  8:55 Stephen Rothwell
2025-07-15 18:54 ` SeongJae Park
2025-07-10  7:54 Stephen Rothwell
2025-07-10 22:30 ` Andrew Morton
2025-07-10 22:49   ` Stephen Rothwell
2025-07-11  0:36   ` Randy Dunlap
2025-07-11  6:28   ` David Hildenbrand
2025-06-10  4:33 Stephen Rothwell
2025-06-10  4:35 ` Christoph Hellwig
2025-05-09  9:43 Stephen Rothwell
2025-05-09 20:31 ` Andrew Morton

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=d96e2916-2c43-462c-b6a1-2375ef397d8b@redhat.com \
    --to=david@redhat$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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