From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Compile fix for 64b dma-fence seqno
Date: Fri, 07 Dec 2018 14:43:43 +0200 [thread overview]
Message-ID: <87h8fptslc.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20181207123907.6829.83545@emeril.freedesktop.org>
Patchwork <patchwork@emeril.freedesktop.org> writes:
> == Series Details ==
>
> Series: drm/i915: Compile fix for 64b dma-fence seqno
> URL : https://patchwork.freedesktop.org/series/53750/
> State : failure
>
> == Summary ==
>
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> CHK include/generated/compile.h
> CC [M] drivers/gpu/drm/i915/i915_gem_context.o
> In file included from ./include/linux/list.h:9:0,
> from ./include/linux/agp_backend.h:33,
> from ./include/drm/drmP.h:35,
> from drivers/gpu/drm/i915/i915_gem_context.c:89:
> drivers/gpu/drm/i915/i915_gem_context.c: In function ‘last_request_on_engine’:
> drivers/gpu/drm/i915/i915_gem_context.c:652:13: error: format ‘%llu’ expects argument of type ‘long long unsigned int’, but argument 5 has type ‘unsigned int’ [-Werror=format=]
> GEM_TRACE("last request for %s on engine %s: %llx:%llu\n",
> ^
Please BAT, fast forward to present?
-Mika
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-12-07 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 12:34 [PATCH] drm/i915: Compile fix for 64b dma-fence seqno Mika Kuoppala
2018-12-07 12:39 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-12-07 12:43 ` Mika Kuoppala [this message]
2018-12-07 13:20 ` Chris Wilson
2018-12-07 12:40 ` [PATCH] " Koenig, Christian
2018-12-07 12:52 ` Chris Wilson
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=87h8fptslc.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.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 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.