Subject: Re: next-20170131 build: 2 failures 3 warnings (next-20170131)

From: Dave Jiang <[email-masked]>
Date: Tue, 31 Jan 2017 12:18:07 -0700

On 01/31/2017 12:10 PM, Mark Brown wrote:
> On Tue, Jan 31, 2017 at 10:33:28AM +0000, Build bot for Mark Brown wrote:
> 
> Today's -next fails to build an arm allmodconfig due to:
> 
>> 	arm-allmodconfig
>> ../drivers/hsi/clients/cmt_speech.c:1114:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
>> ../drivers/gpu/drm/armada/armada_gem.c:38:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
>> ../drivers/gpu/drm/etnaviv/etnaviv_drv.c:468:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
>> ../drivers/gpu/drm/etnaviv/etnaviv_gem.c:178:5: error: conflicting types for 'etnaviv_gem_fault'
>> ../drivers/gpu/drm/omapdrm/omap_drv.c:696:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
>> ../drivers/gpu/drm/omapdrm/omap_gem.c:531:5: error: conflicting types for 'omap_gem_fault'
> 
> which is triggered by 25d3db7600b87 (mm, fs: reduce fault, page_mkwrite,
> and pfn_mkwrite to take only vmf) which updates the signature for fault
> but doesn't update all the users.
> 

I think this patch posted by Arnd should've fixed it
http://ozlabs.org/~akpm/mmots/broken-out/mm-fs-reduce-fault-page_mkwrite-and-pfn_mkwrite-to-take-only-vmf-fix.patch