From: Mel Gorman <mgorman@suse.de>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Aaron Lu <aaron.lu@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [aaron:for_lkp_skl_2sp2_test 151/225] drivers/net/ethernet/netronome/nfp/nfp_net_common.c:1188:34: error: '__GFP_COLD' undeclared; did you mean '__GFP_COMP'?
Date: Thu, 4 Jan 2018 09:56:07 +0000 [thread overview]
Message-ID: <20180104095607.57f64ngwbfwm2jx2@suse.de> (raw)
In-Reply-To: <201801041745.WvR1n84H%fengguang.wu@intel.com>
On Thu, Jan 04, 2018 at 05:25:47PM +0800, kbuild test robot wrote:
> tree: aaron/for_lkp_skl_2sp2_test
> head: 6c9381b65892222cbe2214fb22af9043f9ce1065
> commit: cebd3951aaa6936a2dd70e925a5d5667b896da23 [151/225] mm: remove __GFP_COLD
> config: x86_64-randconfig-x009-201800 (attached as .config)
> compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
> reproduce:
> git checkout cebd3951aaa6936a2dd70e925a5d5667b896da23
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
This looks like a backport of some description. __GFP_COLD is removed in
all cases in mainline so I'm guessing this is specific to Aaron's tree.
The fix is to eliminate __GFP_COLD and just use GFP_KERNEL.
--
Mel Gorman
SUSE Labs
--
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 prev parent reply other threads:[~2018-01-04 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 9:25 kbuild test robot
2018-01-04 9:56 ` Mel Gorman [this message]
2018-01-04 13:13 ` Lu, Aaron
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=20180104095607.57f64ngwbfwm2jx2@suse.de \
--to=mgorman@suse.de \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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