From: Keith Packard <keithp@keithp.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel drivers <Intel-gfx@lists.freedesktop.org>
Subject: Re: IVB Forcewake IRQ patches merged to drm-intel-fixes
Date: Fri, 20 Jan 2012 10:21:55 -0800 [thread overview]
Message-ID: <8639bakzek.fsf@sumi.keithp.com> (raw)
In-Reply-To: <20120120093507.GB4151@phenom.ffwll.local>
[-- Attachment #1.1: Type: text/plain, Size: 335 bytes --]
On Fri, 20 Jan 2012 10:35:07 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> The last patch to revert the busy-loop w/a from Eric is missing your sob
> line. You can also add Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch> to
> it if you want.
Thanks! I've updated the drm-intel-fixes branch.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2012-01-20 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 5:22 IVB Forcewake IRQ patches merged to drm-intel-fixes Keith Packard
2012-01-20 9:35 ` Daniel Vetter
2012-01-20 18:21 ` Keith Packard [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=8639bakzek.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
/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.