public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Mike Kravetz <mike.kravetz@oracle•com>
Subject: Re: linux-next: build warning after merge of the mm-stable tree
Date: Tue, 22 Aug 2023 09:52:43 -0700	[thread overview]
Message-ID: <20230822095243.2b2f5f96ebb6ea7024b8e619@linux-foundation.org> (raw)
In-Reply-To: <20230822165355.5eb8cac1@canb.auug.org.au>

On Tue, 22 Aug 2023 16:53:55 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:

> Hi all,
> 
> After merging the mm-stable tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> mm/hugetlb.c:1: warning: no structured comments found
> 
> Introduced by commit
> 
>   9c5ccf2db04b ("mm: remove HUGETLB_PAGE_DTOR")

Seems we removed the last /** comment from hugetlb.c.

Probably htmldocs just shouldn't warn about this.

otoh, hugetlb.c has undocumented EXPORT_SYMBOLs, so a nice
fix would be to document at least those interfaces....

  reply	other threads:[~2023-08-22 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  6:53 linux-next: build warning after merge of the mm-stable tree Stephen Rothwell
2023-08-22 16:52 ` Andrew Morton [this message]
2023-08-22 17:27   ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2025-01-16  6:05 Stephen Rothwell
2025-01-16 15:10 ` Suren Baghdasaryan
2025-01-16 18:29   ` Suren Baghdasaryan

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=20230822095243.2b2f5f96ebb6ea7024b8e619@linux-foundation.org \
    --to=akpm@linux-foundation$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mike.kravetz@oracle$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=willy@infradead$(echo .)org \
    /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