From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/pxp: Add MTL PXP Support
Date: Wed, 11 Jan 2023 18:20:26 +0000 [thread overview]
Message-ID: <1f86d4d1e450ad651d81237c078a19f08b834c94.camel@intel.com> (raw)
In-Reply-To: <167340073995.20086.4611124861319935926@emeril.freedesktop.org>
Forgot to test with .config PXP set to off - will re-rev
On Wed, 2023-01-11 at 01:32 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/pxp: Add MTL PXP Support
> URL : https://patchwork.freedesktop.org/series/112647/
> State : failure
>
> == Summary ==
>
> Error: make failed
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> CC [M] drivers/gpu/drm/i915/gt/intel_gt_irq.o
> In file included from drivers/gpu/drm/i915/gt/intel_gt_irq.c:16:
> ./drivers/gpu/drm/i915/pxp/intel_pxp_irq.h:42:21: error: expected
> ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘intel_pxp_get_irq_gt’
> 42 | struct intel_gt *gt intel_pxp_get_irq_gt(struct intel_pxp
> *pxp)
> | ^~~~~~~~~~~~~~~~~~~~
> make[5]: *** [scripts/Makefile.build:252:
> drivers/gpu/drm/i915/gt/intel_gt_irq.o] Error 1
> make[4]: *** [scripts/Makefile.build:504: drivers/gpu/drm/i915] Error
> 2
> make[3]: *** [scripts/Makefile.build:504: drivers/gpu/drm] Error 2
> make[2]: *** [scripts/Makefile.build:504: drivers/gpu] Error 2
> make[1]: *** [scripts/Makefile.build:504: drivers] Error 2
> make: *** [Makefile:2008: .] Error 2
>
>
prev parent reply other threads:[~2023-01-11 18:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 0:56 [Intel-gfx] [PATCH 0/9] drm/i915/pxp: Add MTL PXP Support Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 1/9] drm/i915/pxp: Add MTL PXP GSC-CS back-end skeleton Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 2/9] drm/i915/pxp: Add GSC-CS back-end resource init and cleanup Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 3/9] drm/i915/pxp: Add MTL hw-plumbing enabling for KCR operation Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 4/9] drm/i915/pxp: Add MTL helpers to submit Heci-Cmd-Packet to GSC Alan Previn
2023-01-11 5:43 ` kernel test robot
2023-01-11 0:56 ` [Intel-gfx] [PATCH 5/9] drm/i915/pxp: Add GSC-CS backend-teelink for send-message function Alan Previn
2023-01-11 7:44 ` kernel test robot
2023-01-11 0:56 ` [Intel-gfx] [PATCH 5/9] drm/i915/pxp: Add GSC-CS backend to send GSC fw messages Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 6/9] drm/i915/pxp: Add ARB session creation with new PXP API Ver4.3 Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 7/9] drm/i915/pxp: MTL-KCR interrupt ctrl's are in GT-0 Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 7/9] drm/i915/pxp: MTL-KCR is in media-tile but IRQ-ctrl's in root Alan Previn
2023-01-11 4:02 ` kernel test robot
2023-01-11 0:56 ` [Intel-gfx] [PATCH 8/9] drm/i915/pxp: On MTL, KCR enabling doesn't wait on tee component Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 8/9] drm/i915/pxp: On MTL, KCR HW can be enabled instantly Alan Previn
2023-01-11 0:56 ` [Intel-gfx] [PATCH 9/9] drm/i915/pxp: Enable PXP with MTL-GSC-CS Alan Previn
2023-01-11 1:32 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/pxp: Add MTL PXP Support Patchwork
2023-01-11 18:20 ` Teres Alexis, Alan Previn [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=1f86d4d1e450ad651d81237c078a19f08b834c94.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@lists.freedesktop.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