From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"Arunpravin Paneer Selvam" <Arunpravin.PaneerSelvam@amd.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com
Subject: Re: [PATCH 1/3] Revert "drm/amdgpu: move internal vram_mgr function into the C file"
Date: Tue, 26 Jul 2022 09:41:02 +0100 [thread overview]
Message-ID: <52b519d6-ea46-35a9-81fd-256a44937dbd@linux.intel.com> (raw)
In-Reply-To: <d78e0eab-74b8-443b-950a-7adaf963e595@suse.de>
On 26/07/2022 08:46, Thomas Zimmermann wrote:
> Hi
>
> Am 25.07.22 um 19:14 schrieb Christian König:
>> Am 25.07.22 um 17:27 schrieb Tvrtko Ursulin:
>>>
>>> On 24/07/2022 19:28, Thomas Zimmermann wrote:
>>>> Hi
>>>>
>>>> Am 22.07.22 um 17:47 schrieb Christian König:
>>>>> Hi Tvrtko,
>>>>>
>>>>> scratching my head what exactly is going on here.
>>>>>
>>>>> I've build tested drm-tip a couple of test in the last week and it
>>>>> always worked flawlessly.
>>>>>
>>>>> It looks like that some conflict resolution is sometimes not
>>>>> applied correctly, but I have no idea why.
>>>>
>>>> It worked last week, but must have been reintroduced meanhwile.
>>>> Please fetch the latest drm-tip and rebuild. The attached config
>>>> produces the error on my system.
>>>
>>> What is the status with this? I hit a conflict on an implicated file
>>> just now trying to rebuild drm-tip:
>>>
>>> Unmerged paths:
>>> (use "git add/rm <file>..." as appropriate to mark resolution)
>>> deleted by us: drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.h
>>>
>>> I had an other i915 conflict to solve and as grep amdgpu_vram_mgr.h
>>> drivers/gpu/drm/amd produced nothing I just did a git rm on it and
>>> pushed the resolution.
>>>
>>> Let me know if I broke something, re-broke something, or whatever..
>>> Build of amdgpu certainly still looks broken on my end, both before
>>> and after me rebuilding drm-tip so maybe I just preserved the breakage.
>>
>> It looks like that somehow re-broke, but I'm not sure how.
>>
>> I've fetched drm-tip on Friday at around 1pm CET and build it and that
>> worked perfectly fine.
>>
>> Essentially the status of drm-misc-next for the following files should
>> be carried on in drm-tip:
>>
>> drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h
>> drivers/gpu/drm/amd/amdgpu/amdgpu_res_cursor.h
>> drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c
>> drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.h
>
> I've reset these files to their state as in drm-misc-next and updated
> drm-tip. It appears to be working again from what I could test locally.
> Please try at your earliest convenience.
Builds for me now - thank you!
Regards,
Tvrtko
prev parent reply other threads:[~2022-07-26 8:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 9:30 [PATCH 1/3] Revert "drm/amdgpu: move internal vram_mgr function into the C file" Arunpravin Paneer Selvam
2022-07-08 9:30 ` [PATCH 2/3] Revert "drm/amdgpu: fix start calculation in amdgpu_vram_mgr_new" Arunpravin Paneer Selvam
2022-07-08 9:30 ` [PATCH 3/3] Revert "drm/amdgpu: add drm buddy support to amdgpu" Arunpravin Paneer Selvam
2022-07-08 12:26 ` Christian König
2022-07-08 9:33 ` [PATCH 1/3] Revert "drm/amdgpu: move internal vram_mgr function into the C file" Christian König
2022-07-08 10:23 ` Arunpravin Paneer Selvam
2022-07-14 8:45 ` Thomas Zimmermann
2022-07-22 14:46 ` Tvrtko Ursulin
2022-07-22 15:47 ` Christian König
2022-07-24 18:28 ` Thomas Zimmermann
2022-07-25 15:27 ` Tvrtko Ursulin
2022-07-25 17:14 ` Christian König
2022-07-26 7:46 ` Thomas Zimmermann
2022-07-26 8:41 ` Tvrtko Ursulin [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=52b519d6-ea46-35a9-81fd-256a44937dbd@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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.