From: Adam Jackson <ajax-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Chris Wilson <chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org>
Cc: intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
xorg-announce-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
xorg-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [Intel-gfx] xf86-video-intel 2.20.6
Date: Tue, 04 Sep 2012 09:52:10 -0400 [thread overview]
Message-ID: <5046078A.6070104@redhat.com> (raw)
In-Reply-To: <20120902094044.GA18816-URlbQmG4Sm7WRO974kIhX517BDgkB7fE@public.gmane.org>
On 9/2/12 5:40 AM, Chris Wilson wrote:
> * Incoherent concurrent access with the CPU and GPU
> https://bugs.freedesktop.org/show_bug.cgi
> https://bugs.freedesktop.org/show_bug.cgi
Which bugs were these meant to be?
- ajax
next prev parent reply other threads:[~2012-09-04 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 9:40 [ANNOUNCE] xf86-video-intel 2.20.6 Chris Wilson
[not found] ` <20120902094044.GA18816-URlbQmG4Sm7WRO974kIhX517BDgkB7fE@public.gmane.org>
2012-09-04 13:52 ` Adam Jackson [this message]
2012-09-04 13:56 ` [Intel-gfx] " Chris Wilson
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=5046078A.6070104@redhat.com \
--to=ajax-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=chris-Y6uKTt2uX1cEflXRtASbqLVCufUGDwFn@public.gmane.org \
--cc=intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=xorg-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=xorg-announce-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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