public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead•org>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	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 18:27:43 +0100	[thread overview]
Message-ID: <ZOTwDxMdCd5EEjHu@casper.infradead.org> (raw)
In-Reply-To: <20230822095243.2b2f5f96ebb6ea7024b8e619@linux-foundation.org>

On Tue, Aug 22, 2023 at 09:52:43AM -0700, Andrew Morton wrote:
> Seems we removed the last /** comment from hugetlb.c.

Heh, yeah, two of my own patches colliding.  That's what I get for
working on the mm in two different git trees at the same time.

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

Ask and ye shall receive.  I decided not to document
linear_hugepage_index() since Sidhartha is deleting the only
user of it, and it was never an interface that was widely used.
Hopefully we're rid of PageHuge sometime soon.

  reply	other threads:[~2023-08-22 17:27 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
2023-08-22 17:27   ` Matthew Wilcox [this message]
  -- 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=ZOTwDxMdCd5EEjHu@casper.infradead.org \
    --to=willy@infradead$(echo .)org \
    --cc=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 \
    /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