From: Jani Nikula <jani.nikula@linux.intel.com>
To: kbuild test robot <fengguang.wu@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Dave Airlie <airlied@redhat.com>,
kbuild-all@01.org, dri-devel@lists.freedesktop.org
Subject: Re: [drm:drm-next 2/5] ERROR: "__umoddi3" undefined!
Date: Mon, 31 Oct 2016 12:07:29 +0200 [thread overview]
Message-ID: <87zilkltlq.fsf@intel.com> (raw)
In-Reply-To: <201610311743.46IyQt5w%fengguang.wu@intel.com>
On Mon, 31 Oct 2016, kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: git://people.freedesktop.org/~airlied/linux.git drm-next
> head: fb422950c6cd726fd36eb72a7cf84583440a18a2
> commit: 5481e27f6fd06b7cb902072e81d6b083db8155eb [2/5] Merge tag 'drm-intel-next-2016-10-24' of git://anongit.freedesktop.org/drm-intel into drm-next
> config: i386-allmodconfig (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> git checkout 5481e27f6fd06b7cb902072e81d6b083db8155eb
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "__umoddi3" undefined!
Since
commit 7093f5ff75ae759ef9bdd514f917a1f57cd10d65
Author: Zhenyu Wang <zhenyuw@linux.intel.com>
Date: Fri Oct 21 12:33:56 2016 +0800
drm/i915: GVT-g driver depends on 64BIT kernel
the combination of
# CONFIG_64BIT is not set
CONFIG_DRM_I915_GVT=y
present in the attached config should not be possible.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-10-31 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 9:45 [drm:drm-next 2/5] ERROR: "__umoddi3" undefined! kbuild test robot
2016-10-31 10:07 ` Jani Nikula [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=87zilkltlq.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.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.