From: Luben Tuikov <luben.tuikov@amd.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Alexander Deucher <Alexander.Deucher@amd.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/2] amdgpu's drm_driver becomes const
Date: Wed, 4 Nov 2020 11:24:03 -0500 [thread overview]
Message-ID: <6a43eb32-d3fb-eb5d-aa9a-4846cb643b60@amd.com> (raw)
In-Reply-To: <20201104094314.GM401619@phenom.ffwll.local>
On 2020-11-04 04:43, Daniel Vetter wrote:
> On Tue, Nov 03, 2020 at 10:11:27PM -0500, Luben Tuikov wrote:
>> Hi Daniel,
>>
>> These two patches follow up your latest
>> DRM work to make definitions of struct drm_driver
>> in DRM low-level drivers, constant, in amdgpu.
>>
>> This set doesn't descend from my previous patch
>> "drm/amdgpu: Convert to using devm_drm_dev_alloc() (v2)",
>> since our branch doesn't have it, and I can see
>> that your const patches aren't in drm-next yet,
>> but they are based on my conversion patch.
>> Perhaps you can graft these two patches locally
>> and dispatch them via drm-next. (There'll be
>> a one-line conflict, namely the devm_drm_dev_alloc().)
>
> Ah cool, thanks for doing this. I'll take your series here and include it
> in mine and resend the entire pile.
> -Daniel
Yeah, no problem, my pleasure.
Thanks for picking this up.
Regards,
Luben
>>
>> Thanks and Regards,
>> Luben
>>
>> Alex Deucher (1):
>> drm/amdgpu/virt: fix handling of the atomic flag
>>
>> Luben Tuikov (1):
>> drm/amdgpu: Make struct drm_driver const
>>
>> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 32 +++++++++++++++++++++---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 25 +-----------------
>> drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | 4 ++-
>> 3 files changed, 32 insertions(+), 29 deletions(-)
>>
>> --
>> 2.29.2.154.g7f7ebe054a
>>
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-11-04 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 3:11 [PATCH 0/2] amdgpu's drm_driver becomes const Luben Tuikov
2020-11-04 3:11 ` [PATCH 1/2] drm/amdgpu/virt: fix handling of the atomic flag Luben Tuikov
2020-11-04 3:11 ` [PATCH 2/2] drm/amdgpu: Make struct drm_driver const Luben Tuikov
2020-11-04 10:00 ` Daniel Vetter
2020-11-04 9:43 ` [PATCH 0/2] amdgpu's drm_driver becomes const Daniel Vetter
2020-11-04 16:24 ` Luben Tuikov [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=6a43eb32-d3fb-eb5d-aa9a-4846cb643b60@amd.com \
--to=luben.tuikov@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox