From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/5] Assorted reviewed patches for CI run
Date: Thu, 11 Feb 2016 10:27:27 +0000 [thread overview]
Message-ID: <1455186452-13691-1-git-send-email-tvrtko.ursulin@linux.intel.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
As the subject says, just to trigger a CI run for some assorted
patches which are all already R-Bed.
Tvrtko Ursulin (5):
drm/i915: Use appropriate spinlock flavour
drm/i915: GEM operations need to be done under the big lock
drm/i915: Fix struct mutex vs. RPS lock inversion
drm/i915/guc: Do not wait for firmware load atomically
drm/i915/ilk: Move register read under spinlock
drivers/gpu/drm/i915/i915_gem.c | 6 ++----
drivers/gpu/drm/i915/i915_gem_stolen.c | 2 ++
drivers/gpu/drm/i915/intel_display.c | 12 ++++++------
drivers/gpu/drm/i915/intel_guc_loader.c | 6 +++---
drivers/gpu/drm/i915/intel_pm.c | 15 ++++++++-------
5 files changed, 21 insertions(+), 20 deletions(-)
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-02-11 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 10:27 Tvrtko Ursulin [this message]
2016-02-11 10:27 ` [PATCH 1/5] drm/i915: Use appropriate spinlock flavour Tvrtko Ursulin
2016-02-11 10:27 ` [PATCH 2/5] drm/i915: GEM operations need to be done under the big lock Tvrtko Ursulin
2016-02-11 10:27 ` [PATCH 3/5] drm/i915: Fix struct mutex vs. RPS lock inversion Tvrtko Ursulin
2016-02-11 10:27 ` [PATCH 4/5] drm/i915/guc: Do not wait for firmware load atomically Tvrtko Ursulin
2016-02-11 10:27 ` [PATCH 5/5] drm/i915/ilk: Move register read under spinlock Tvrtko Ursulin
2016-02-15 14:53 ` ✗ Fi.CI.BAT: warning for Assorted reviewed patches for CI run Patchwork
2016-02-15 16:06 ` Tvrtko Ursulin
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=1455186452-13691-1-git-send-email-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).