From: Thomas Hellstrom <thellstrom@vmware.com>
To: Julian Margetson <runaway@candw.ms>,
Alex Deucher <alexdeucher@gmail.com>,
dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH] drm/ttm: use phys_addr_t for ttm_bus_placement
Date: Fri, 1 Apr 2016 18:42:13 +0200 [thread overview]
Message-ID: <56FEA4E5.3050807@vmware.com> (raw)
In-Reply-To: <56FEA25C.3010204@candw.ms>
Acked-by: Thomas Hellstrom <thellstrom@vmware.com>
On 04/01/2016 06:31 PM, Julian Margetson wrote:
> On 4/1/2016 11:02 AM, Alex Deucher wrote:
>> Fixes ttm on platforms like PPC460 where the CPU
>> is in 32-bit mode, but the physical addresses are
>>> 32 bits.
>> Extracted from a patch by Hans.
>>
>> Cc: Thomas Hellstrom <thellstrom@vmware.com>
>> Cc: Julian Margetson <runaway@candw.ms>
>> Cc: Hans Verkuil <hans.verkuil@cisco.com>
>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>> ---
>> include/drm/ttm/ttm_bo_api.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/drm/ttm/ttm_bo_api.h b/include/drm/ttm/ttm_bo_api.h
>> index afae231..055a08d 100644
>> --- a/include/drm/ttm/ttm_bo_api.h
>> +++ b/include/drm/ttm/ttm_bo_api.h
>> @@ -92,7 +92,7 @@ struct ttm_placement {
>> */
>> struct ttm_bus_placement {
>> void *addr;
>> - unsigned long base;
>> + phys_addr_t base;
>> unsigned long size;
>> unsigned long offset;
>> bool is_iomem;
> Tested and working .
> Tested-by: Julian Margetson <runaway@candw.ms>
>
> Regards
> Julian
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-01 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 15:02 [PATCH] drm/ttm: use phys_addr_t for ttm_bus_placement Alex Deucher
2016-04-01 16:31 ` Julian Margetson
2016-04-01 16:42 ` Thomas Hellstrom [this message]
2016-04-01 17:55 ` Christian König
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=56FEA4E5.3050807@vmware.com \
--to=thellstrom@vmware.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hans.verkuil@cisco.com \
--cc=runaway@candw.ms \
/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.