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 Feb 3 (mm, hugepage)
Date: Wed, 3 Feb 2016 10:19:04 -0800 [thread overview]
Message-ID: <56B24498.4040402@infradead.org> (raw)
In-Reply-To: <20160203161811.621b399a@canb.auug.org.au>
On 02/02/16 21:18, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160202:
>
on x86_64:
when CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD is enabled
and CONFIG_TRANSPARENT_HUGEPAGE is not enabled:
../fs/proc/task_mmu.c: In function 'smaps_pud_range':
../fs/proc/task_mmu.c:596:2: error: implicit declaration of function 'is_huge_zero_pud' [-Werror=implicit-function-declaration]
if (is_huge_zero_pud(*pud))
^
--
~Randy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2016-02-03 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160203161811.621b399a@canb.auug.org.au>
2016-02-03 18:19 ` Randy Dunlap [this message]
2016-02-03 18:24 ` linux-next: Tree for Feb 3 (i386: redef. of native_pud_clear) 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=56B24498.4040402@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).