linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Muchun Song <songmuchun@bytedance.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	broonie@kernel.org,
	 linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	 Linux Memory Management List <linux-mm@kvack.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	mhocko@suse.cz,  mm-commits@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [External] Re: mmotm 2021-05-19-23-58 uploaded (mm/migrate.c)
Date: Fri, 21 May 2021 10:22:28 +0800	[thread overview]
Message-ID: <CAMZfGtW=jgjJPUNk4jxFXWZ91wuYEm4q3x7NUVSjGpu0Xjc7hA@mail.gmail.com> (raw)
In-Reply-To: <8e1de6c2-27af-f612-7467-a7d1f1a31bff@infradead.org>

On Fri, May 21, 2021 at 6:21 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 5/19/21 11:59 PM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2021-05-19-23-58 has been uploaded to
> >
> >    https://www.ozlabs.org/~akpm/mmotm/
> >
> > mmotm-readme.txt says
> >
> > README for mm-of-the-moment:
> >
> > https://www.ozlabs.org/~akpm/mmotm/
> >
> > This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> > more than once a week.
> >
> > You will need quilt to apply these patches to the latest Linus release (5.x
> > or 5.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> > https://ozlabs.org/~akpm/mmotm/series
> >
> > The file broken-out.tar.gz contains two datestamp files: .DATE and
> > .DATE-yyyy-mm-dd-hh-mm-ss.  Both contain the string yyyy-mm-dd-hh-mm-ss,
> > followed by the base kernel version against which this patch series is to
> > be applied.
> >
> > This tree is partially included in linux-next.  To see which patches are
> > included in linux-next, consult the `series' file.  Only the patches
> > within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> > linux-next.
>
> on x86_64:
>
> ../mm/migrate.c: In function ‘unmap_and_move_huge_page’:
> ../mm/migrate.c:1295:6: error: implicit declaration of function ‘hugetlb_page_subpool’; did you mean ‘hugetlb_count_sub’? [-Werror=implicit-function-declaration]
>   if (hugetlb_page_subpool(hpage) && !page_mapping(hpage)) {
>       ^~~~~~~~~~~~~~~~~~~~
>
> Full randconfig file is attached.

Thanks. I'll fix it in the next version.

>
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
>


  reply	other threads:[~2021-05-21  2:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  6:59 mmotm 2021-05-19-23-58 uploaded akpm
2021-05-20 22:21 ` mmotm 2021-05-19-23-58 uploaded (mm/migrate.c) Randy Dunlap
2021-05-21  2:22   ` Muchun Song [this message]
2021-05-20 22:40 ` mmotm 2021-05-19-23-58 uploaded (net/netfilter/nft_set_pipapo_avx2.c) Randy Dunlap
2021-05-20 23:07   ` Stephen Rothwell
2021-05-21  1:04     ` Randy Dunlap
2021-05-20 22:53 ` mmotm 2021-05-19-23-58 uploaded (drivers/iio/accel/fxls8962af-core.o) Randy Dunlap

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='CAMZfGtW=jgjJPUNk4jxFXWZ91wuYEm4q3x7NUVSjGpu0Xjc7hA@mail.gmail.com' \
    --to=songmuchun@bytedance.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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