Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] drm/i915: clarify semaphore-ring interaction
Date: Thu, 17 May 2012 14:09:28 +0100	[thread overview]
Message-ID: <1337260170_80289@CP5-2952> (raw)
In-Reply-To: <1337229612-12946-1-git-send-email-ben@bwidawsk.net>

On Wed, 16 May 2012 21:40:12 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> After Daniel split out this code, I think this makes more sense, and
> looks nicer. Also added some comments to help the situation.
> 
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>

The change is an improvement, just looks like it could be simplified...
;-p
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2012-05-17 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  4:40 [PATCH] drm/i915: clarify semaphore-ring interaction Ben Widawsky
2012-05-17 13:09 ` 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=1337260170_80289@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