Updated patch
Reviewed-by: Thomas Hellstrom
On 11/20/2011 10:02 PM, Jerome Glisse wrote:
> On Sat, Nov 19, 2011 at 3:45 PM, Thomas Hellstrom
> wrote:
>
>> On 11/19/2011 12:32 AM, j.glisse at gmail.com wrote:
>>
>>> From: Jerome Glisse
>>>
>>> Previously we were calling back
Updated patch
Reviewed-by: Thomas Hellstrom thellst...@vmware.com
On 11/20/2011 10:02 PM, Jerome Glisse wrote:
On Sat, Nov 19, 2011 at 3:45 PM, Thomas Hellstromthellst...@vmware.com wrote:
On 11/19/2011 12:32 AM, j.gli...@gmail.com wrote:
From: Jerome Glissejgli...@redhat.com
On Sat, Nov 19, 2011 at 3:45 PM, Thomas Hellstrom
wrote:
> On 11/19/2011 12:32 AM, j.glisse at gmail.com wrote:
>>
>> From: Jerome Glisse
>>
>> Previously we were calling back move_notify in error path when the
>> bo is returned to it's original position or when destroy the bo.
>> When
On Sat, Nov 19, 2011 at 3:45 PM, Thomas Hellstrom thellst...@vmware.com wrote:
On 11/19/2011 12:32 AM, j.gli...@gmail.com wrote:
From: Jerome Glissejgli...@redhat.com
Previously we were calling back move_notify in error path when the
bo is returned to it's original position or when destroy
On 11/19/2011 12:32 AM, j.glisse at gmail.com wrote:
> From: Jerome Glisse
>
> Previously we were calling back move_notify in error path when the
> bo is returned to it's original position or when destroy the bo.
> When destroying the bo set the new mem placement as NULL when calling
> back in the
On 11/19/2011 12:32 AM, j.gli...@gmail.com wrote:
From: Jerome Glissejgli...@redhat.com
Previously we were calling back move_notify in error path when the
bo is returned to it's original position or when destroy the bo.
When destroying the bo set the new mem placement as NULL when calling
back
On 11/18/2011 06:32 PM, j.glisse at gmail.com wrote:
> From: Jerome Glisse
>
> Previously we were calling back move_notify in error path when the
> bo is returned to it's original position or when destroy the bo.
> When destroying the bo set the new mem placement as NULL when calling
> back in the
From: Jerome Glisse
Previously we were calling back move_notify in error path when the
bo is returned to it's original position or when destroy the bo.
When destroying the bo set the new mem placement as NULL when calling
back in the driver.
Updating nouveau to deal with
From: Jerome Glisse
Previously we were calling back move_notify in error path when the
bo is returned to it's original position or when destroy the bo.
When destroying the bo set the new mem placement as NULL when calling
back in the driver.
Updating nouveau to deal with
From: Jerome Glisse
Previously we were calling back move_notify in error path when the
bo is returned to it's original position or when destroy the bo.
When destroying the bo set the new mem placement as NULL when calling
back in the driver.
Updating nouveau to deal with
From: Jerome Glisse jgli...@redhat.com
Previously we were calling back move_notify in error path when the
bo is returned to it's original position or when destroy the bo.
When destroying the bo set the new mem placement as NULL when calling
back in the driver.
Updating nouveau to deal with NULL
On 11/18/2011 06:32 PM, j.gli...@gmail.com wrote:
From: Jerome Glissejgli...@redhat.com
Previously we were calling back move_notify in error path when the
bo is returned to it's original position or when destroy the bo.
When destroying the bo set the new mem placement as NULL when calling
back
12 matches
Mail list logo