public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Jerome Glisse <jglisse@redhat.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Dave Airlie" <airlied@redhat.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: linux-next - drm/ttm versus nouveau - WARNING and dead driver.
Date: Thu, 06 May 2010 13:09:15 -0400	[thread overview]
Message-ID: <4162.1273165755@localhost> (raw)
In-Reply-To: Your message of "Thu, 06 May 2010 18:56:10 +0200." <20100506165610.GB8934@barney.localdomain>

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

On Thu, 06 May 2010 18:56:10 +0200, Jerome Glisse said:
> On Thu, May 06, 2010 at 06:16:26PM +0200, Rafał Miłecki wrote:
> > 2010/5/6  <Valdis.Kletnieks@vt.edu>:
> > > Bisected down to:
> > >
> > > 82c5da6bf8b55a931b042fb531083863d26c8020 is the first bad commit
> > > commit 82c5da6bf8b55a931b042fb531083863d26c8020
> > > Author: Jerome Glisse <jglisse@redhat.com>
> > > Date:   Fri Apr 9 14:39:23 2010 +0200
> > >
> > >    drm/ttm: ttm_fault callback to allow driver to handle bo placement V6
> > 
> > Can this be duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=27822
 ?
> > 
> > -- 
> > Rafał
> 
> Yes this is a duplicate of :
> https://bugs.freedesktop.org/show_bug.cgi?id=27822
> 
> The patch attached in the bug should fix your issue. Sorry for the
> trouble.

Confirming that the patch does fix the problem, thanks.

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

      reply	other threads:[~2010-05-06 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 16:06 linux-next - drm/ttm versus nouveau - WARNING and dead driver Valdis.Kletnieks
2010-05-06 16:16 ` Rafał Miłecki
2010-05-06 16:56   ` Jerome Glisse
2010-05-06 17:09     ` Valdis.Kletnieks [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=4162.1273165755@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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