From: Matthew Auld <matthew.auld@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/selftests: Fixup naked 64b divide
Date: Mon, 14 Oct 2019 09:15:55 +0100 [thread overview]
Message-ID: <91819aad-3e51-8341-ca4e-d66ebf79af0f@intel.com> (raw)
In-Reply-To: <20191013114509.3405-1-chris@chris-wilson.co.uk>
On 13/10/2019 12:45, Chris Wilson wrote:
> drivers/gpu/drm/i915/intel_memory_region.o: in function `igt_mock_contiguous':
> drivers/gpu/drm/i915/selftests/intel_memory_region.c:166: undefined reference to `__umoddi3'
>
> v2: promote target to u64 for consistency across all builds
>
> Reported-by: kbuild test robot <lkp@intel.com>
> Fixes: 2f0b97ca0211 ("drm/i915/region: support contiguous allocations")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-14 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 9:11 [PATCH] drm/i915/selftests: Fixup naked 64b divide Chris Wilson
2019-10-13 9:56 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-10-13 9:56 ` ✗ Fi.CI.BUILD: warning " Patchwork
2019-10-13 11:45 ` [PATCH v2] " Chris Wilson
2019-10-14 8:15 ` Matthew Auld [this message]
2019-10-14 8:25 ` ✓ Fi.CI.IGT: success for " Patchwork
2019-10-14 15:44 ` ✗ Fi.CI.BAT: failure for drm/i915/selftests: Fixup naked 64b divide (rev2) 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=91819aad-3e51-8341-ca4e-d66ebf79af0f@intel.com \
--to=matthew.auld@intel.com \
--cc=chris@chris-wilson.co.uk \
--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