From: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@linux.intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: RE: [PATCH v3 0/8] Support for transparent PUD pages for DAX files
Date: Wed, 27 Jan 2016 20:53:09 +0000 [thread overview]
Message-ID: <100D68C7BA14664A8938383216E40DE04217CB7B@FMSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <20160127123933.bcfef2fe5bcdc5bb6714eec7@linux-foundation.org>
Yeah, I need to rebase. Please drop for now, I'll resend tomorrow.
See you Monday, I assume ;-)
-----Original Message-----
From: Andrew Morton [mailto:akpm@linux-foundation.org]
Sent: Wednesday, January 27, 2016 12:40 PM
To: Wilcox, Matthew R; Matthew Wilcox; linux-mm@kvack.org; linux-nvdimm@ml01.01.org; linux-fsdevel@vger.kernel.org; linux-kernel@vger.kernel.org; x86@kernel.org
Subject: Re: [PATCH v3 0/8] Support for transparent PUD pages for DAX files
On Wed, 27 Jan 2016 12:31:31 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> Just from eyeballing the patches, I'm expecting build errors ;)
Didn't take long :(
mm/memory.c: In function 'zap_pud_range':
mm/memory.c:1216: error: implicit declaration of function 'pud_trans_huge'
mm/memory.c:1217: error: 'HPAGE_PUD_SIZE' undeclared (first use in this function)
and, midway:
include/linux/mm.h:348: error: redefinition of 'pud_devmap'
include/asm-generic/pgtable.h:684: note: previous definition of 'pud_devmap' was here
Please run x86_64 allnoconfig at each step of the series, fix and
respin? It only takes 30s to compile.
--
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>
prev parent reply other threads:[~2016-01-27 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 19:49 Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 1/8] mm: Convert an open-coded VM_BUG_ON_VMA Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 2/8] mm,fs,dax: Change ->pmd_fault to ->huge_fault Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 3/8] mm: Add support for PUD-sized transparent hugepages Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 4/8] mincore: Add support for PUDs Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 5/8] procfs: Add support for PUDs to smaps, clear_refs and pagemap Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 6/8] x86: Add support for PUD-sized transparent hugepages Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 7/8] dax: Support for transparent PUD pages Matthew Wilcox
2016-01-08 19:49 ` [PATCH v3 8/8] ext4: Support for PUD-sized transparent huge pages Matthew Wilcox
2016-01-15 19:41 ` [PATCH v3 0/8] Support for transparent PUD pages for DAX files Darrick J. Wong
2016-01-22 11:26 ` Dave Chinner
2016-01-21 22:48 ` mingming cao
2016-01-22 14:11 ` Matthew Wilcox
2016-01-27 20:31 ` Andrew Morton
2016-01-27 20:39 ` Andrew Morton
2016-01-27 20:53 ` Wilcox, Matthew R [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=100D68C7BA14664A8938383216E40DE04217CB7B@FMSMSX114.amr.corp.intel.com \
--to=matthew.r.wilcox@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=willy@linux.intel.com \
--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