From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/7] drm/i915: use intel_uncore in fw get/put internal paths
Date: Wed, 20 Mar 2019 22:55:25 -0000 [thread overview]
Message-ID: <20190320225525.27757.35366@emeril.freedesktop.org> (raw)
In-Reply-To: <20190320211407.25316-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [CI,1/7] drm/i915: use intel_uncore in fw get/put internal paths
URL : https://patchwork.freedesktop.org/series/58295/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: use intel_uncore in fw get/put internal paths
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3559:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3564:16: warning: expression using sizeof(void)
Commit: drm/i915: use intel_uncore for all forcewake get/put
Okay!
Commit: drm/i915: make more uncore function work on intel_uncore
Okay!
Commit: drm/i915: make find_fw_domain work on intel_uncore
Okay!
Commit: drm/i915: reduce the dev_priv->uncore dance in uncore.c
Okay!
Commit: drm/i915: move regs pointer inside the uncore structure
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3564:16: warning: expression using sizeof(void)
+drivers/gpu/drm/i915/selftests/../i915_drv.h:3562:16: warning: expression using sizeof(void)
Commit: drm/i915: make raw access function work on uncore
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-03-20 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 21:14 [CI 1/7] drm/i915: use intel_uncore in fw get/put internal paths Chris Wilson
2019-03-20 21:14 ` [CI 2/7] drm/i915: use intel_uncore for all forcewake get/put Chris Wilson
2019-03-20 21:14 ` [CI 3/7] drm/i915: make more uncore function work on intel_uncore Chris Wilson
2019-03-20 21:14 ` [CI 4/7] drm/i915: make find_fw_domain " Chris Wilson
2019-03-20 21:14 ` [CI 5/7] drm/i915: reduce the dev_priv->uncore dance in uncore.c Chris Wilson
2019-03-20 21:14 ` [CI 6/7] drm/i915: move regs pointer inside the uncore structure Chris Wilson
2019-03-20 21:14 ` [CI 7/7] drm/i915: make raw access function work on uncore Chris Wilson
2019-03-20 22:51 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/7] drm/i915: use intel_uncore in fw get/put internal paths Patchwork
2019-03-20 22:55 ` Patchwork [this message]
2019-03-20 23:12 ` ✗ Fi.CI.BAT: failure " 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=20190320225525.27757.35366@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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 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.