All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Gordon <david.s.gordon@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 0/5] Add GuC ADS (Addition Data Structure)
Date: Tue, 5 Jan 2016 11:35:48 +0100	[thread overview]
Message-ID: <20160105103548.GV8076@phenom.ffwll.local> (raw)
In-Reply-To: <568AC3E1.1000601@intel.com>

On Mon, Jan 04, 2016 at 07:11:29PM +0000, Dave Gordon wrote:
> On 18/12/15 20:00, yu.dai@intel.com wrote:
> >From: Alex Dai <yu.dai@intel.com>
> >
> >The GuC firmware uses this for various purposes. The ADS itself is a chunk of
> >memory created by driver to share with GuC. This series creates the GuC ADS
> >object and setup some basic settings for it.
> >
> >This version addresses some comments from Chris W. Tidy up some code; replace
> >kmap_atomic by kmap etc.
> >
> >Alex Dai (4):
> >   drm/i915/guc: Add GuC ADS (Addition Data Structure) - allocation
> >   drm/i915/guc: Add GuC ADS - scheduler policies
> >   drm/i915/guc: Add GuC ADS - MMIO reg state
> >   drm/i915/guc: Add GuC ADS - enabling ADS
> >
> >Dave Gordon (1):
> >   drm/i915/guc: Expose (intel)_lr_context_size()
> >
> >  drivers/gpu/drm/i915/i915_guc_reg.h        |   1 +
> >  drivers/gpu/drm/i915/i915_guc_submission.c |  95 ++++++++++++++++++++++++
> >  drivers/gpu/drm/i915/intel_guc.h           |   2 +
> >  drivers/gpu/drm/i915/intel_guc_fwif.h      | 113 ++++++++++++++++++++++++++++-
> >  drivers/gpu/drm/i915/intel_guc_loader.c    |   7 ++
> >  drivers/gpu/drm/i915/intel_lrc.c           |   4 +-
> >  drivers/gpu/drm/i915/intel_lrc.h           |   1 +
> >  7 files changed, 220 insertions(+), 3 deletions(-)
> >
> 
> For the whole series,
> 
> Reviewed-by: Dave Gordon <david.s.gordon@intel.com>

All 5 merged to dinq, thanks.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-01-05 10:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 20:00 [PATCH v2 0/5] Add GuC ADS (Addition Data Structure) yu.dai
2015-12-18 20:00 ` [PATCH v2 1/5] drm/i915/guc: Expose (intel)_lr_context_size() yu.dai
2016-01-05 10:27   ` Daniel Vetter
2016-01-05 12:21     ` [PATCH] drm/i915: add kerneldoc for intel_lr_context_size() Dave Gordon
2016-01-05 13:57       ` Daniel Vetter
2016-01-05 18:35     ` [PATCH v2 1/5] drm/i915/guc: Expose (intel)_lr_context_size() Yu Dai
2016-01-05 18:33   ` [PATCH v3] " yu.dai
2016-01-06  7:38     ` Daniel Vetter
2015-12-18 20:00 ` [PATCH v2 2/5] drm/i915/guc: Add GuC ADS (Addition Data Structure) - allocation yu.dai
2015-12-18 20:00 ` [PATCH v2 3/5] drm/i915/guc: Add GuC ADS - scheduler policies yu.dai
2015-12-18 20:00 ` [PATCH v2 4/5] drm/i915/guc: Add GuC ADS - MMIO reg state yu.dai
2015-12-18 20:00 ` [PATCH v2 5/5] drm/i915/guc: Add GuC ADS - enabling ADS yu.dai
2015-12-19  8:49 ` ✗ warning: Fi.CI.BAT Patchwork
2016-01-04 19:11 ` [PATCH v2 0/5] Add GuC ADS (Addition Data Structure) Dave Gordon
2016-01-05 10:35   ` Daniel Vetter [this message]
2016-01-05 12:30 ` ✗ failure: Fi.CI.BAT Patchwork
2016-01-06  9:01 ` 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=20160105103548.GV8076@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=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 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.