From: Patchwork <patchwork@emeril.freedesktop.org>
To: Xiaolin Zhang <xiaolin.zhang@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for i915 vgpu PV to improve vgpu performance
Date: Mon, 29 Jul 2019 08:22:38 -0000 [thread overview]
Message-ID: <20190729082238.26658.35940@emeril.freedesktop.org> (raw)
In-Reply-To: <1564417962-74325-1-git-send-email-xiaolin.zhang@intel.com>
== Series Details ==
Series: i915 vgpu PV to improve vgpu performance
URL : https://patchwork.freedesktop.org/series/64372/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: introduced vgpu pv capability
Okay!
Commit: drm/i915: vgpu shared memory setup for pv optimization
Okay!
Commit: drm/i915: vgpu pv command buffer support
Okay!
Commit: drm/i915: vgpu ppgtt update pv optimization
Okay!
Commit: drm/i915: vgpu context submission pv optimization
Okay!
Commit: drm/i915/gvt: GVTg handle pv_caps PVINFO register
Okay!
Commit: drm/i915/gvt: GVTg handle shared_page setup
Okay!
Commit: drm/i915/gvt: GVTg support ppgtt pv optimization
+./include/linux/slab.h:672:13: error: undefined identifier '__builtin_mul_overflow'
+./include/linux/slab.h:672:13: warning: call with no type!
Commit: drm/i915/gvt: GVTg support context submission pv optimization
Okay!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-29 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 16:32 [PATCH v9 0/9] i915 vgpu PV to improve vgpu performance Xiaolin Zhang
2019-07-29 8:18 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-07-29 8:22 ` Patchwork [this message]
2019-07-29 12:21 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-29 14:43 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-29 16:32 ` [PATCH v9 1/9] drm/i915: introduced vgpu pv capability Xiaolin Zhang
2019-07-29 16:32 ` [PATCH v9 2/9] drm/i915: vgpu shared memory setup for pv optimization Xiaolin Zhang
2019-07-29 16:32 ` [PATCH v9 3/9] drm/i915: vgpu pv command buffer support Xiaolin Zhang
2019-07-29 16:32 ` [PATCH v9 4/9] drm/i915: vgpu ppgtt update pv optimization Xiaolin Zhang
2019-07-29 16:32 ` [PATCH v9 5/9] drm/i915: vgpu context submission " Xiaolin Zhang
2019-07-29 16:32 ` [PATCH v9 6/9] drm/i915/gvt: GVTg handle pv_caps PVINFO register Xiaolin Zhang
2019-07-29 16:32 ` [PATCH v9 7/9] drm/i915/gvt: GVTg handle shared_page setup Xiaolin Zhang
2019-07-29 16:32 ` [PATCH v9 8/9] drm/i915/gvt: GVTg support ppgtt pv optimization Xiaolin Zhang
2019-07-29 16:32 ` [PATCH v9 9/9] drm/i915/gvt: GVTg support context submission " Xiaolin Zhang
-- strict thread matches above, loose matches on Subject: below --
2019-07-23 11:31 [PATCH v8 0/9] i915 vgpu PV to improve vgpu performance Xiaolin Zhang
2019-07-23 3:17 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-07-08 1:35 [PATCH v7 0/8] " Xiaolin Zhang
2019-07-08 1:52 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-06-03 6:02 [PATCH v6 0/8] " Xiaolin Zhang
2019-06-03 7:27 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-04-29 3:10 [PATCH v5 0/8] " Xiaolin Zhang
2019-04-29 12:34 ` ✗ Fi.CI.SPARSE: warning for " 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=20190729082238.26658.35940@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=xiaolin.zhang@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