Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/i915: clarify semaphore-ring interaction
Date: Mon, 21 May 2012 22:40:45 +0100	[thread overview]
Message-ID: <1337636454_167127@CP5-2952> (raw)
In-Reply-To: <20120521140305.7421ef30@bwidawsk.net>

On Mon, 21 May 2012 14:03:05 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> I can do that. Are you okay with the idea otherwise? This is really all
> prep work for some HSW patches anyway.

Yes, I can see where you are going, I just need that little bit of
convincing that it will all work out in the end ;-)
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2012-05-21 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20 13:52 [PATCH v3] drm/i915: clarify semaphore-ring interaction Ben Widawsky
2012-05-20 15:45 ` [PATCH v4] " Ben Widawsky
2012-05-21  8:44   ` Chris Wilson
2012-05-21 21:03     ` Ben Widawsky
2012-05-21 21:40       ` Chris Wilson [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=1337636454_167127@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=ben@bwidawsk.net \
    --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