From: Dave Jiang <dave.jiang@intel.com>
To: Mark Brown <broonie@kernel.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: next-20170131 build: 2 failures 3 warnings (next-20170131)
Date: Tue, 31 Jan 2017 12:18:07 -0700 [thread overview]
Message-ID: <d75e33ae-45ec-af7a-9ad1-1b8e54285b0c@intel.com> (raw)
In-Reply-To: <20170131191021.ogodwklhn74o5ws5@sirena.org.uk>
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
next prev parent reply other threads:[~2017-01-31 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 10:33 next-20170131 build: 2 failures 3 warnings (next-20170131) Build bot for Mark Brown
2017-01-31 19:10 ` Mark Brown
2017-01-31 19:18 ` Dave Jiang [this message]
2017-02-01 7:27 ` Stephen Rothwell
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=d75e33ae-45ec-af7a-9ad1-1b8e54285b0c@intel.com \
--to=dave.jiang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
/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