public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Siluvery, Arun" <arun.siluvery@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] A few fixes on top of the wa_regs patches
Date: Wed, 3 Sep 2014 12:40:13 +0200	[thread overview]
Message-ID: <20140903104013.GL15520@phenom.ffwll.local> (raw)
In-Reply-To: <5406DCF7.2060206@linux.intel.com>

On Wed, Sep 03, 2014 at 10:18:47AM +0100, Siluvery, Arun wrote:
> On 30/08/2014 16:50, Damien Lespiau wrote:
> >Hi Arun,
> >
> >I've compiled a few patches that I think solve some small-ish issues around
> >your wa_regs series. Could you please have a look at them and comment/give your
> >r-b tag if you judge appropriate?
> >
> >On top of those patches, I'd love some comments on the issues I raised in the
> >other mail and possible follow up patches to address them.
> >
> >   http://lists.freedesktop.org/archives/intel-gfx/2014-August/051514.html
> >
> >At some point, we'll also need a bit of coherence with what Mika has been doing:
> >
> >   http://lists.freedesktop.org/archives/intel-gfx/2014-August/050000.html
> >
> Hi Daniel,
> 
> Since the new workaround design/implementation takes time could you please
> pull the patches in this series to fix the issues and also the patch to
> change filename in igt.

Yes this is the best approach since clarifying what exactly the full blown
w/a infrastructure should do will take a bit of time.

> for the series,
> Reviewed-by: Arun Siluvery <arun.siluvery@linux.intel.com>

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-09-03 10:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-30 15:50 [PATCH 0/5] A few fixes on top of the wa_regs patches Damien Lespiau
2014-08-30 15:50 ` [PATCH 1/5] drm/i915: Rename intel_wa_registers with a i915_ prefix Damien Lespiau
2014-09-01 11:06   ` Siluvery, Arun
2014-08-30 15:51 ` [PATCH 2/5] drm/i915: Don't overrun the intel_wa_regs array Damien Lespiau
2014-08-30 15:51 ` [PATCH 3/5] drm/i915: Don't silently discard workarounds Damien Lespiau
2014-08-30 15:51 ` [PATCH 4/5] drm/i915: Remove unneeded brackets Damien Lespiau
2014-08-30 15:51 ` [PATCH 5/5] drm/i915: Don't restrict i915_wa_registers to BDW Damien Lespiau
2014-09-01 11:33   ` Siluvery, Arun
2014-08-31 19:32 ` [PATCH 0/5] A few fixes on top of the wa_regs patches Siluvery, Arun
2014-09-01  9:08   ` Daniel Vetter
2014-09-01  9:29     ` Siluvery, Arun
2014-09-03  9:18 ` Siluvery, Arun
2014-09-03 10:40   ` 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=20140903104013.GL15520@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=arun.siluvery@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --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