Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Open-code i915_gpu_idle() for handling seqno wrapping
Date: Mon, 10 Dec 2012 11:59:44 +0000	[thread overview]
Message-ID: <f5ae8a$7plv4f@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1355140577-6572-2-git-send-email-mika.kuoppala@intel.com>

On Mon, 10 Dec 2012 13:56:17 +0200, Mika Kuoppala <mika.kuoppala@linux.intel.com> wrote:
> From: Chris Wilson <chris@chris-wilson.co.uk>
> @@ -2032,6 +2032,7 @@ i915_add_request(struct intel_ring_buffer *ring,
>  	}
>  
>  	trace_i915_gem_request_add(ring, request->seqno);
> +	dev_priv->last_seqno = request->seqno;

An unnecessary addition to my patch.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-12-10 11:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 11:56 [PATCH 1/2] drm/i915: Don't emit semaphore wait if wrap happened Mika Kuoppala
2012-12-10 11:56 ` [PATCH 2/2] drm/i915: Open-code i915_gpu_idle() for handling seqno wrapping Mika Kuoppala
2012-12-10 11:59   ` Chris Wilson [this message]
2012-12-10 14:01     ` Mika Kuoppala

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='f5ae8a$7plv4f@fmsmga002.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@linux.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