From: Daniel Vetter <daniel@ffwll.ch>
To: oscar.mateo@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/6] Execlists prep-work
Date: Thu, 22 May 2014 23:45:03 +0200 [thread overview]
Message-ID: <20140522214503.GL14357@phenom.ffwll.local> (raw)
In-Reply-To: <1400764418-30061-1-git-send-email-oscar.mateo@intel.com>
On Thu, May 22, 2014 at 02:13:32PM +0100, oscar.mateo@intel.com wrote:
> From: Oscar Mateo <oscar.mateo@intel.com>
>
> These patches contain refactoring and preparatory work for Execlists [1].
>
> [1http://lists.freedesktop.org/archives/intel-gfx/2014-May/044847.html]
> http://lists.freedesktop.org/archives/intel-gfx/2014-May/044847.html
All merged to dinq, thanks.
-Daniel
>
> Oscar Mateo (6):
> drm/i915: s/intel_ring_buffer/intel_engine_cs
> drm/i915: Split the ringbuffers from the rings (1/3)
> drm/i915: Split the ringbuffers from the rings (2/3)
> drm/i915: Split the ringbuffers from the rings (3/3)
> drm/i915: s/i915_hw_context/intel_context
> drm/i915: Kill private_default_ctx off
>
> drivers/gpu/drm/i915/i915_cmd_parser.c | 24 +-
> drivers/gpu/drm/i915/i915_debugfs.c | 29 +--
> drivers/gpu/drm/i915/i915_dma.c | 33 +--
> drivers/gpu/drm/i915/i915_drv.h | 55 +++--
> drivers/gpu/drm/i915/i915_gem.c | 62 +++---
> drivers/gpu/drm/i915/i915_gem_context.c | 64 +++---
> drivers/gpu/drm/i915/i915_gem_execbuffer.c | 24 +-
> drivers/gpu/drm/i915/i915_gem_gtt.c | 18 +-
> drivers/gpu/drm/i915/i915_gem_gtt.h | 4 +-
> drivers/gpu/drm/i915/i915_gem_render_state.c | 2 +-
> drivers/gpu/drm/i915/i915_gpu_error.c | 12 +-
> drivers/gpu/drm/i915/i915_irq.c | 36 +--
> drivers/gpu/drm/i915/i915_sysfs.c | 2 +-
> drivers/gpu/drm/i915/i915_trace.h | 26 +--
> drivers/gpu/drm/i915/intel_display.c | 18 +-
> drivers/gpu/drm/i915/intel_drv.h | 4 +-
> drivers/gpu/drm/i915/intel_overlay.c | 12 +-
> drivers/gpu/drm/i915/intel_pm.c | 10 +-
> drivers/gpu/drm/i915/intel_ringbuffer.c | 318 +++++++++++++++------------
> drivers/gpu/drm/i915/intel_ringbuffer.h | 127 ++++++-----
> drivers/gpu/drm/i915/intel_uncore.c | 2 +-
> 21 files changed, 465 insertions(+), 417 deletions(-)
>
> --
> 1.9.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-05-22 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 13:13 [PATCH 0/6] Execlists prep-work oscar.mateo
2014-05-22 13:13 ` [PATCH 1/6] drm/i915: s/intel_ring_buffer/intel_engine_cs oscar.mateo
2014-05-22 13:13 ` [PATCH 2/6] drm/i915: Split the ringbuffers from the rings (1/3) oscar.mateo
2014-05-22 13:13 ` [PATCH 3/6] drm/i915: Split the ringbuffers from the rings (2/3) oscar.mateo
2014-05-22 21:28 ` Daniel Vetter
2014-05-22 13:13 ` [PATCH 4/6] drm/i915: Split the ringbuffers from the rings (3/3) oscar.mateo
2014-05-22 21:37 ` Daniel Vetter
2014-05-22 21:44 ` Daniel Vetter
2014-05-22 13:13 ` [PATCH 5/6] drm/i915: s/i915_hw_context/intel_context oscar.mateo
2014-05-22 21:39 ` Daniel Vetter
2014-05-22 13:13 ` [PATCH 6/6] drm/i915: Kill private_default_ctx off oscar.mateo
2014-05-22 21:45 ` Daniel Vetter [this message]
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=20140522214503.GL14357@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscar.mateo@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