All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Print error state times relative to capture
Date: Wed, 02 May 2018 11:34:21 +0300	[thread overview]
Message-ID: <871seuzcaa.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <152484312871.7427.6931122178899223452@mail.alporthouse.com>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> Quoting Mika Kuoppala (2018-04-27 16:12:48)
>> @@ -427,8 +428,10 @@ static void error_print_context(struct drm_i915_error_state_buf *m,
>>  }
>>  
>>  static void error_print_engine(struct drm_i915_error_state_buf *m,
>> -                              const struct drm_i915_error_engine *ee)
>> +                              const struct i915_gpu_state *error,
>> +                              const int engine_n)
>
> Make it pass in the error_engine again, and

Done.

> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Thanks for review. Pushed.
-Mika

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-05-02  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 15:12 [PATCH] drm/i915: Print error state times relative to capture Mika Kuoppala
2018-04-27 15:32 ` Chris Wilson
2018-05-02  8:34   ` Mika Kuoppala [this message]
2018-04-27 15:38 ` ✓ Fi.CI.BAT: success for drm/i915: Print error state times relative to capture (rev2) Patchwork
2018-04-27 19:16 ` ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2018-04-16 13:40 [PATCH] drm/i915: Print error state times relative to capture Mika Kuoppala
2018-04-16 13:52 ` Chris Wilson

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=871seuzcaa.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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.