From: Dan Williams Subject: Re: [PATCH] mm: replace FAULT_FLAG_SIZE with parameter to huge_fault Date: Fri, 3 Feb 2017 15:26:55 -0800 Message-ID: References: <201702040648.oOjnlEcm%fengguang.wu@intel.com> <2020f442-8e77-cf14-a6b1-b4b00d0da80b@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: kbuild test robot , kbuild-all@01.org, Andrew Morton , Matthew Wilcox , "linux-nvdimm@lists.01.org" , Dave Hansen , linux-xfs@vger.kernel.org, Linux MM , "Kirill A. Shutemov" , Jan Kara , linux-ext4 , Ross Zwisler , Vlastimil Babka To: Dave Jiang Return-path: Received: from mail-oi0-f42.google.com ([209.85.218.42]:33364 "EHLO mail-oi0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752785AbdBCX04 (ORCPT ); Fri, 3 Feb 2017 18:26:56 -0500 Received: by mail-oi0-f42.google.com with SMTP id w204so19956392oiw.0 for ; Fri, 03 Feb 2017 15:26:56 -0800 (PST) In-Reply-To: <2020f442-8e77-cf14-a6b1-b4b00d0da80b@intel.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Fri, Feb 3, 2017 at 3:25 PM, Dave Jiang wrote: > On 02/03/2017 03:56 PM, kbuild test robot wrote: >> Hi Dave, >> >> [auto build test ERROR on mmotm/master] >> [cannot apply to linus/master linux/master v4.10-rc6 next-20170203] >> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] > > This one is a bit odd. I just pulled mmotm tree master branch and built > with the attached .config and it passed for me (and I don't see this > commit in the master branch). I also built linux-next with this patch on > top and it also passes with attached .config. Looking at the err log > below it seems the code has a mix of partial from before and after the > patch. I'm rather confused about it.... This is a false positive. It tried to build it against latest mainline instead of linux-next.