Re: [mmotm:master 203/305] mm/memcontrol.c:5629:52: error: 'THP_FAULT_ALLOC' undeclared; did you mean 'THP_FILE_ALLOC'?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [mmotm:master 203/305] mm/memcontrol.c:5629:52: error: 'THP_FAULT_ALLOC' undeclared; did you mean 'THP_FILE_ALLOC'?
From: Chris Down <chris@xxxxxxxxxxxxxx>
Date: Thu, 31 Jan 2019 14:09:02 -0500
Cc: kbuild test robot <lkp@xxxxxxxxx>, kbuild-all@xxxxxx, Johannes Weiner <hannes@xxxxxxxxxxx>, Linux Memory Management List <linux-mm@xxxxxxxxx>
In-reply-to: <20190131110757.6b975f1e787dc7adf414a162@linux-foundation.org>
References: <201902010206.hcZ8gj0z%fengguang.wu@intel.com> <20190131110757.6b975f1e787dc7adf414a162@linux-foundation.org>
User-agent: Mutt/1.11.2 (2019-01-07)

Andrew Morton writes:

Thanks.    This, I assume:

That might be desirable as well, but it's mostly because of lack of guard onCONFIG_TRANSPARENT_HUGEPAGES :-)

References:
- [mmotm:master 203/305] mm/memcontrol.c:5629:52: error: 'THP_FAULT_ALLOC' undeclared; did you mean 'THP_FILE_ALLOC'?
  - From: kbuild test robot
- Re: [mmotm:master 203/305] mm/memcontrol.c:5629:52: error: 'THP_FAULT_ALLOC' undeclared; did you mean 'THP_FILE_ALLOC'?
  - From: Andrew Morton

Prev by Date: Re: [mmotm:master 203/305] mm/memcontrol.c:5629:52: error: 'THP_FAULT_ALLOC' undeclared; did you mean 'THP_FILE_ALLOC'?
Next by Date: Re: [RFC PATCH 3/5] mm/vma: add support for peer to peer to device vma
Previous by thread: Re: [mmotm:master 203/305] mm/memcontrol.c:5629:52: error: 'THP_FAULT_ALLOC' undeclared; did you mean 'THP_FILE_ALLOC'?
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux