From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Dave Hansen <dave.hansen@intel.com>
Subject: Re: linux-next: Tree for Nov 28 (arch/x86/mm/kaiser.c)
Date: Tue, 28 Nov 2017 08:47:54 -0800 [thread overview]
Message-ID: <7e969f86-1208-e5ea-3ee3-b9f9c73c3285@infradead.org> (raw)
In-Reply-To: <20171128145247.21f5e888@canb.auug.org.au>
On 11/27/2017 07:52 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20171127:
>
> New trees: ntb, kvm-master, at24
>
on x86_64:
../arch/x86/mm/kaiser.c: In function 'kaiser_shadow_pagetable_walk':
../arch/x86/mm/kaiser.c:173:28: error: '__GFP_NOTRACK' undeclared (first use in this function)
gfp_t gfp = (GFP_KERNEL | __GFP_NOTRACK | __GFP_ZERO);
--
~Randy
next prev parent reply other threads:[~2017-11-28 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 3:52 linux-next: Tree for Nov 28 Stephen Rothwell
2017-11-28 16:47 ` Randy Dunlap [this message]
2017-11-28 17:08 ` linux-next: Tree for Nov 28 (arch/x86/mm/kaiser.c) Thomas Gleixner
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=7e969f86-1208-e5ea-3ee3-b9f9c73c3285@infradead.org \
--to=rdunlap@infradead.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@kernel.org \
/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).