From: "Zhang, Jerry (Junwei)" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: Felix Kuehling <felix.kuehling-5C7GfCeVMHo@public.gmane.org>,
Oded Gabbay <oded.gabbay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Deucher,
Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
Dave Airlie <airlied-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: KFD co-maintainership and branch model
Date: Thu, 23 Aug 2018 09:54:49 +0800 [thread overview]
Message-ID: <5B7E13E9.5050803@amd.com> (raw)
In-Reply-To: <705cc9da-7ccb-bafd-0dd8-86630b37a8ca-5C7GfCeVMHo@public.gmane.org>
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
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-08-23 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 22:25 KFD co-maintainership and branch model Felix Kuehling
[not found] ` <705cc9da-7ccb-bafd-0dd8-86630b37a8ca-5C7GfCeVMHo@public.gmane.org>
2018-08-23 1:34 ` David Airlie
[not found] ` <CAMwc25pqgoahob6NeJEB5DXr3R05gA05ZRMsgq-dsjWFUusZeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-08-23 6:54 ` Oded Gabbay
[not found] ` <CAFCwf11FJpeDyFazspQNo26SNN7CA-CVpFMoKn2Q6hcNX6ymDA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-08-23 7:00 ` Christian König
[not found] ` <fdddff79-44f5-46ec-7a0b-b7695edd4219-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-08-23 12:38 ` Deucher, Alexander
[not found] ` <BN6PR12MB180964F09192A0BFDA4D0A8BF7370-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-08-24 21:57 ` Felix Kuehling
[not found] ` <ab96b343-a1cb-6f69-cac6-36f27e04ff29-5C7GfCeVMHo@public.gmane.org>
2018-08-27 14:28 ` Deucher, Alexander
2018-08-23 1:54 ` Zhang, Jerry (Junwei) [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=5B7E13E9.5050803@amd.com \
--to=jerry.zhang-5c7gfcevmho@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=airlied-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=felix.kuehling-5C7GfCeVMHo@public.gmane.org \
--cc=oded.gabbay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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.