From: Patchwork <patchwork@emeril.freedesktop.org>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for drm/i915: expose RCS topology to userspace (rev2)
Date: Mon, 26 Feb 2018 18:52:49 -0000 [thread overview]
Message-ID: <20180226185249.27510.21525@emeril.freedesktop.org> (raw)
In-Reply-To: <20180226175711.15380-1-lionel.g.landwerlin@intel.com>
== Series Details ==
Series: drm/i915: expose RCS topology to userspace (rev2)
URL : https://patchwork.freedesktop.org/series/38981/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/i915: store all subslice masks
Okay!
Commit: drm/i915/debugfs: reuse max slice/subslices already stored in sseu
-
+drivers/gpu/drm/i915/i915_debugfs.c:4341:29: warning: Variable length array is used.
+drivers/gpu/drm/i915/i915_debugfs.c:4342:22: warning: Variable length array is used.
+drivers/gpu/drm/i915/i915_debugfs.c:4396:29: warning: Variable length array is used.
+drivers/gpu/drm/i915/i915_debugfs.c:4397:22: warning: Variable length array is used.
Commit: drm/i915/debugfs: add rcs topology entry
Okay!
Commit: drm/i915: add rcs topology to error state
Okay!
Commit: drm/i915: add query uAPI
+drivers/gpu/drm/i915/i915_query.c:14:5: warning: symbol 'i915_query_ioctl' was not declared. Should it be static?
Commit: drm/i915: expose rcs topology through query uAPI
-O:drivers/gpu/drm/i915/i915_query.c:14:5: warning: symbol 'i915_query_ioctl' was not declared. Should it be static?
+drivers/gpu/drm/i915/i915_query.c:96:5: warning: symbol 'i915_query_ioctl' was not declared. Should it be static?
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-26 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 17:57 [PATCH v15 0/6] drm/i915: expose RCS topology to userspace Lionel Landwerlin
2018-02-26 17:57 ` [PATCH v15 1/6] drm/i915: store all subslice masks Lionel Landwerlin
2018-02-26 18:28 ` [PATCH v16 " Lionel Landwerlin
2018-02-26 17:57 ` [PATCH v15 2/6] drm/i915/debugfs: reuse max slice/subslices already stored in sseu Lionel Landwerlin
2018-02-26 17:57 ` [PATCH v15 3/6] drm/i915/debugfs: add rcs topology entry Lionel Landwerlin
2018-02-26 17:57 ` [PATCH v15 4/6] drm/i915: add rcs topology to error state Lionel Landwerlin
2018-02-26 17:57 ` [PATCH v15 5/6] drm/i915: add query uAPI Lionel Landwerlin
2018-02-26 17:57 ` [PATCH v15 6/6] drm/i915: expose rcs topology through " Lionel Landwerlin
2018-02-26 18:05 ` ✗ Fi.CI.BAT: failure for drm/i915: expose RCS topology to userspace Patchwork
2018-02-26 18:52 ` Patchwork [this message]
2018-02-26 19:05 ` ✓ Fi.CI.BAT: success for drm/i915: expose RCS topology to userspace (rev2) Patchwork
2018-02-26 22:45 ` ✓ Fi.CI.IGT: " 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=20180226185249.27510.21525@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@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