From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: warning for drm/i915/dp: debug log max vswing and pre-emphasis
Date: Sat, 18 Jan 2020 00:11:20 -0000 [thread overview]
Message-ID: <157930628038.11511.15143481064862884377@emeril.freedesktop.org> (raw)
In-Reply-To: <20200117150235.22471-1-jani.nikula@intel.com>
== Series Details ==
Series: drm/i915/dp: debug log max vswing and pre-emphasis
URL : https://patchwork.freedesktop.org/series/72191/
State : warning
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
CHK include/generated/compile.h
Kernel: arch/x86/boot/bzImage is ready (#1)
Building modules, stage 2.
MODPOST 122 modules
ERROR: "__udivdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!
scripts/Makefile.modpost:93: recipe for target '__modpost' failed
make[1]: *** [__modpost] Error 1
Makefile:1282: recipe for target 'modules' failed
make: *** [modules] Error 2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16156/build_32bit.log
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-18 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 15:02 [Intel-gfx] [PATCH] drm/i915/dp: debug log max vswing and pre-emphasis Jani Nikula
2020-01-18 0:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-18 0:11 ` Patchwork [this message]
2020-01-20 18:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-01-21 14:32 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2020-01-21 15:49 ` Jani Nikula
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=157930628038.11511.15143481064862884377@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).