From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Ben Widawsky <ben@bwidawsk.net>,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [RFC] drm/i915: opencode get/put irq for gen6+
Date: Thu, 29 Mar 2012 21:32:50 +0100 [thread overview]
Message-ID: <1333053184_146777@CP5-2952> (raw)
In-Reply-To: <1333049209-1978-1-git-send-email-ben@bwidawsk.net>
On Thu, 29 Mar 2012 12:26:49 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> Before Chris get's all mad and complains that I did the opposite with
> semaphores - semaphores did have a bit of logic which many had found
> confusing and it was greatly simplified by abstracting it.
>
> Anyhow, this removes a few lines that really didn't serve much purpose.
Yup, looks a worthwhile saving.
> It also seems I can collapse the GT and GEN6 interrupt definitions into
> 1, but I'll have to check, and it's a separate patch anyway.
But that's the patch I've been waiting for too long now! And I think
this patch would look even better afterwards.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-03-29 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 19:26 [RFC] drm/i915: opencode get/put irq for gen6+ Ben Widawsky
2012-03-29 20:32 ` 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=1333053184_146777@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--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