From: Chris Wilson <chris@chris-wilson.co.uk>
To: Eric Anholt <eric@anholt.net>, Dave Airlie <airlied@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [git pull] i915 fixes
Date: Sat, 12 Feb 2011 18:35:33 +0000 [thread overview]
Message-ID: <849307$bhtvgm@azsmga001.ch.intel.com> (raw)
In-Reply-To: <87mxm22eke.fsf@pollan.anholt.net>
On Fri, 11 Feb 2011 18:04:49 -0800, Eric Anholt <eric@anholt.net> wrote:
> On Fri, 11 Feb 2011 09:58:03 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > Dave, a few more days have passed and we have a fresh batch of
> > regression fixes.
> >
> > The patch that is most notable is one for its absence:
> >
> > commit 25ed6eb15ebc4472fb0e473666c0ef3bba87097f
> > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > Date: Wed Dec 22 11:37:09 2010 +0000
> >
> > agp/intel: Experiment with a 855GM GWB bit
> >
> > is still sitting on drm-intel-staging just begging for someone with an
> > 865g to give it the once over.
>
> Tested-by: Eric Anholt <eric@anholt.net>
Thanks a lot Eric! Knowing that it does not cause 865g to spontaneously
burst into flames makes me feel a lot more comfortable with it.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-02-12 18:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 9:58 [git pull] i915 fixes Chris Wilson
2011-02-12 2:04 ` Eric Anholt
2011-02-12 18:35 ` Chris Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-07 12:00 Chris Wilson
2011-03-07 21:28 ` Jim Gettys
2011-03-08 4:00 ` Dave Airlie
2011-03-08 19:47 ` Jesse Barnes
2011-03-08 4:08 ` Jim Gettys
2011-03-08 7:27 ` Dave Airlie
2011-03-08 8:32 ` Chris Wilson
2011-03-01 23:56 Chris Wilson
2011-02-24 1:09 Chris Wilson
2011-02-24 15:06 ` Jesse Barnes
2011-02-01 9:44 Chris Wilson
2010-12-30 19:01 Chris Wilson
2010-12-30 22:01 ` Jesse Barnes
2010-12-30 22:18 ` Chris Wilson
2010-12-30 22:29 ` Linus Torvalds
2010-12-30 22:53 ` 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='849307$bhtvgm@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@redhat.com \
--cc=eric@anholt.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 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.