From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Linux MM <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Nov 26 (mm/page_owner.c)
Date: Thu, 26 Nov 2015 08:05:05 -0800 [thread overview]
Message-ID: <56572DB1.5070605@infradead.org> (raw)
In-Reply-To: <20151126161655.281096bb@canb.auug.org.au>
On 11/25/15 21:16, Stephen Rothwell wrote:
> Hi all,
>
> Reminder: there will be no linux-next release next week (Nov 30 - Dec 4).
>
> Changes since 20151124:
>
on i386:
mm/built-in.o: In function `read_page_owner':
page_owner.c:(.text+0x25d89): undefined reference to `migrate_reason_names'
mm/built-in.o: In function `__dump_page_owner':
(.text+0x26137): undefined reference to `migrate_reason_names'
when CONFIG_MIGRATION is not enabled.
--
~Randy
prev parent reply other threads:[~2015-11-26 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 5:16 linux-next: Tree for Nov 26 Stephen Rothwell
2015-11-26 16:05 ` Randy Dunlap [this message]
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=56572DB1.5070605@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).