From: Jani Nikula <jani.nikula@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Patchwork <patchwork@emeril.freedesktop.org>,
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for linux-next: build failure after merge of the drm-misc tree
Date: Tue, 18 Jun 2019 11:11:59 +0300 [thread overview]
Message-ID: <87k1djtir4.fsf@intel.com> (raw)
In-Reply-To: <20190614164253.1f8364ab@canb.auug.org.au>
On Fri, 14 Jun 2019, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> On Fri, 14 Jun 2019 04:47:35 -0000 Patchwork <patchwork@emeril.freedesktop.org> wrote:
>>
>> == Series Details ==
>>
>> Series: linux-next: build failure after merge of the drm-misc tree
>> URL : https://patchwork.freedesktop.org/series/62080/
>> State : failure
>>
>> == Summary ==
>>
>> CALL scripts/checksyscalls.sh
>> CALL scripts/atomic/check-atomics.sh
>> DESCEND objtool
>> CHK include/generated/compile.h
>> CC [M] drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.o
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4024:18: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
>> .atomic_check = amdgpu_dm_connector_atomic_check,
>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4024:18: note: (near initialization for ‘amdgpu_dm_connector_helper_funcs.atomic_check’)
>> cc1: some warnings being treated as errors
>> scripts/Makefile.build:278: recipe for target 'drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.o' failed
>> make[4]: *** [drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.o] Error 1
>> scripts/Makefile.build:489: recipe for target 'drivers/gpu/drm/amd/amdgpu' failed
>> make[3]: *** [drivers/gpu/drm/amd/amdgpu] Error 2
>> scripts/Makefile.build:489: recipe for target 'drivers/gpu/drm' failed
>> make[2]: *** [drivers/gpu/drm] Error 2
>> scripts/Makefile.build:489: recipe for target 'drivers/gpu' failed
>> make[1]: *** [drivers/gpu] Error 2
>> Makefile:1071: recipe for target 'drivers' failed
>> make: *** [drivers] Error 2
>>
>
> Can someone please stop this CI from trying to validate linux-next
> merge fix patches ...
Half the complaints are about CI trying to validate too much, and the
other half are about not validating enough...
Arek?
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-18 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 4:41 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2019-06-14 4:41 ` Stephen Rothwell
2019-06-14 4:47 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-06-14 6:42 ` Stephen Rothwell
2019-06-18 8:11 ` Jani Nikula [this message]
2019-08-07 3:21 Stephen Rothwell
2019-08-07 3:48 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-08-28 8:55 Stephen Rothwell
2019-08-28 15:27 ` ✗ Fi.CI.BAT: failure for " Patchwork
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=87k1djtir4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.