KFD co-maintainership and branch model

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/23/2018 06:25 AM, Felix Kuehling wrote:
> Hi all,
>
> Oded has offered to make me co-maintainer of KFD, as he's super busy at
> work and less responsive than he used to be.
>
> At the same time we're about to send out the first patches to merge KFD
> and AMDGPU into a single kernel module.
>
> With that in mind I'd like to propose to upstream KFD through Alex's
> branch in the future. It would avoid conflicts in shared code
> (amdgpu_vm.c is most active at the moment) when merging branches, and
> make the code flow and testing easier.
>
> Please let me know what you think?

Shall we share the same style as DC upstream in amdgpu?

For the common code like amdgpu_vm.c, it's ideally to work for both KFD and amdgpu gfx.
If a patch impacts gfx performance but improves compute ability, we may reserve that
as a hybrid patch for production release only.

Regards,
Jerry

>
> Regards,
>    Felix
>


[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux