From: "Christian König" <christian.koenig@amd.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Not 100% sure if I correctly fixed drm-tip
Date: Fri, 12 Feb 2021 08:51:19 +0100 [thread overview]
Message-ID: <64da0f52-e2e9-b7cb-d104-52079896041a@amd.com> (raw)
In-Reply-To: <CAKMK7uEAMST0dOzFDuRYoDh=QgGDQm-7qepfaF+wAnJwbSTGzw@mail.gmail.com>
Am 11.02.21 um 18:22 schrieb Daniel Vetter:
> On Thu, Feb 11, 2021 at 4:27 PM Christian König
> <christian.koenig@amd.com> wrote:
>>
>>
>> Am 11.02.21 um 16:02 schrieb Jani Nikula:
>>> On Thu, 11 Feb 2021, Christian König <christian.koenig@amd.com> wrote:
>>>> Hi guys,
>>>>
>>>> I had a conflict this morning in the ttm pool while pushing an important
>>>> fix to drm-misc-fixes.
>>>>
>>>> I'm not 100% sure if I correctly fixed up drm-tip. How can this be
>>>> double checked? And how can it be fixed if the merge has gone bad?
>>> I'm afraid there's a problem; bb52cb0dec8d ("drm/ttm: make the pool
>>> shrinker lock a mutex") in upstream and drm-misc-fixes creates a silent
>>> conflict with ba051901d10f ("drm/ttm: add a debugfs file for the global
>>> page pools") in drm-misc-next, causing the latter to use
>>> spin_lock/unlock on a mutex.
>>>
>>> But while you hit a conflict, it does look like the conflict breaking
>>> the build is silent, AFAICT the spinlock part does not conflict. So a
>>> fixup patch in drm-rerere is probably needed until there are some
>>> backmerges.
>> Well exactly that's the issue. I've already had a fixup in drm-rerere
>> for this.
>>
>> But today I've pushed another fix to drm-misc-fixes which also conflicts
>> with ba051901d10f ("drm/ttm: add a debugfs file for the global page pools").
>>
>> I've fixed this up as well and committed the solution. But dim then
>> complained that the original fixup is now not applicable any more (which
>> is true as far as I know).
>>
>> This somehow went away when I said that dim should assume patch
>> reversal, but I'm not sure if that's the right thing to do.
> Nothing, it's all still broken. You need to delete the now unecessary
> fixup. As a rule, when rebuilding drm-tip failed always try again to
> confirm that what you've done actually fixed things (since sometimes
> git can also not remember where to apply the resolution for some odd
> reasons).
My question is how to I remove the fixup now?
E.g. where can I find it?
Thanks,
Christian.
>
> I'm fixing this now.
> -Daniel
>
>> Thanks,
>> Christian.
>>
>>>
>>> BR,
>>> Jani.
>>>
>>>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-02-12 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 10:01 Not 100% sure if I correctly fixed drm-tip Christian König
2021-02-11 14:37 ` Thomas Zimmermann
2021-02-11 15:02 ` Jani Nikula
2021-02-11 15:27 ` Christian König
2021-02-11 17:22 ` Daniel Vetter
2021-02-12 7:51 ` Christian König [this message]
2021-02-12 8:27 ` Daniel Vetter
2021-02-12 8:32 ` Christian König
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=64da0f52-e2e9-b7cb-d104-52079896041a@amd.com \
--to=christian.koenig@amd.com \
--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