From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/3] (Final) tidying up of GuC code
Date: Mon, 12 Sep 2016 21:19:34 +0100 [thread overview]
Message-ID: <1473711577-11454-1-git-send-email-david.s.gordon@intel.com> (raw)
Mostly renaming the GuC functions to use a more consistent naming
scheme, along with updating comments to clarify some of the code.
Dave Gordon (3):
drm/i915: clarify PMINTRMSK/pm_intr_keep usage
drm/i915/guc: general tidying up (loader)
drm/i915/guc: general tidying up (submission)
drivers/gpu/drm/i915/i915_drv.h | 1 +
drivers/gpu/drm/i915/i915_guc_reg.h | 3 --
drivers/gpu/drm/i915/i915_guc_submission.c | 63 +++++++++++++++---------------
drivers/gpu/drm/i915/i915_irq.c | 4 +-
drivers/gpu/drm/i915/i915_reg.h | 2 +-
drivers/gpu/drm/i915/intel_guc.h | 2 +-
drivers/gpu/drm/i915/intel_guc_loader.c | 54 +++++++++++++++++--------
drivers/gpu/drm/i915/intel_lrc.c | 2 +-
8 files changed, 75 insertions(+), 56 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-09-12 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 20:19 Dave Gordon [this message]
2016-09-12 20:19 ` [PATCH 1/3] drm/i915: clarify PMINTRMSK/pm_intr_keep usage Dave Gordon
2016-09-14 15:06 ` Tvrtko Ursulin
2016-09-12 20:19 ` [PATCH 2/3] drm/i915/guc: general tidying up (loader) Dave Gordon
2016-09-14 15:12 ` Tvrtko Ursulin
2016-09-12 20:19 ` [PATCH 3/3] drm/i915/guc: general tidying up (submission) Dave Gordon
2016-09-14 15:22 ` Tvrtko Ursulin
2016-09-14 17:00 ` Dave Gordon
2016-09-15 8:57 ` Tvrtko Ursulin
2016-09-15 10:04 ` Chris Wilson
2016-09-12 21:20 ` ✓ Fi.CI.BAT: success for (Final) tidying up of GuC code 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=1473711577-11454-1-git-send-email-david.s.gordon@intel.com \
--to=david.s.gordon@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).