Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [regression] drm/i915/execbuffer: Reorder binding of objects to favour restrictions
Date: Sun, 16 Jan 2011 15:55:57 +0100	[thread overview]
Message-ID: <1295189757.7721.0.camel@zwerg> (raw)
In-Reply-To: <0d30dc$kp25lf@orsmga001.jf.intel.com>

Am Sonntag, den 16.01.2011, 14:53 +0000 schrieb Chris Wilson:
> On Sun, 16 Jan 2011 15:38:34 +0100, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> > Hi Chris,
> > did you got my regression report?
> 
> It appears you didn't get my response saying Linus had already pulled the
> fix.
> -Chris
> 

Ah, ok.

Then the fix is not in drm-intel-next

-- 
Regards,
        Alexey

  reply	other threads:[~2011-01-16 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 15:11 [regression] drm/i915/execbuffer: Reorder binding of objects to favour restrictions Alexey Fisher
2011-01-16 14:38 ` Alexey Fisher
2011-01-16 14:53   ` Chris Wilson
2011-01-16 14:55     ` Alexey Fisher [this message]
2011-01-16 15:02       ` 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=1295189757.7721.0.camel@zwerg \
    --to=bug-track@fisher-privat.net \
    --cc=chris@chris-wilson.co.uk \
    --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