On Sun, Sep 17, 2017 at 9:37 PM, Alex Deucher wrote:
> On Sat, Sep 16, 2017 at 11:58 AM, Oded Gabbay wrote:
>> On Mon, Sep 4, 2017 at 10:50 AM, Daniel Vetter wrote:
>>> Hi Alex,
>>>
>>> Since Dave is out, can you just pull that into the amd pile?
>>> -Daniel
>>>
>>
>> Hi Alex,
>> Did you take th
On Sat, Sep 16, 2017 at 11:58 AM, Oded Gabbay wrote:
> On Mon, Sep 4, 2017 at 10:50 AM, Daniel Vetter wrote:
>> Hi Alex,
>>
>> Since Dave is out, can you just pull that into the amd pile?
>> -Daniel
>>
>
> Hi Alex,
> Did you take the patches to your pile ?
> If not, I'll ping Dave again as it see
On Mon, Sep 4, 2017 at 10:50 AM, Daniel Vetter wrote:
> Hi Alex,
>
> Since Dave is out, can you just pull that into the amd pile?
> -Daniel
>
Hi Alex,
Did you take the patches to your pile ?
If not, I'll ping Dave again as it seems he is back to work (at least
partially).
Oded
> On Sat, Sep 02,
Hi Alex,
Since Dave is out, can you just pull that into the amd pile?
-Daniel
On Sat, Sep 02, 2017 at 04:29:38PM +0300, Oded Gabbay wrote:
> Hi Dave,
>
> Three more amdkfd commits for the 4.14 merge window, nothing too major:
>
> - Removing redundant memset before memcpy
> - Passing valid mqd p
Hi Dave,
Three more amdkfd commits for the 4.14 merge window, nothing too major:
- Removing redundant memset before memcpy
- Passing valid mqd pointer to destroy_mqd function (fix apply to VI cards)
- Replace uint32_t and uint64_t with __u32 and __u64 respectively in kfd_ioctl.h
Thanks,
Oded
Th
Hi Dave,
This is the amdkfd pull request for 4.14 merge window.
AMD has started cleaning the pipe and sending patches from their internal
development to the upstream community.
The plan as I understand it is to first get all the non-dGPU patches to
upstream and then move to upstream dGPU support.
