All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>,
	Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: michel@daenzer.net, Borislav Petkov <bp@alien8.de>,
	amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: grab extra fence reference for drm_sched_job_add_dependency
Date: Fri, 6 Jan 2023 16:27:50 +0100	[thread overview]
Message-ID: <f4c965d9-d985-0030-7411-6d8d0f750058@gmail.com> (raw)
In-Reply-To: <CADnq5_P0Nq-y1U5X4EgYyPSKXOdVsjxX+UOCmzZKnX8FfHC86w@mail.gmail.com>

Am 06.01.23 um 15:24 schrieb Alex Deucher:
> On Fri, Jan 6, 2023 at 8:00 AM Mikhail Gavrilov
> <mikhail.v.gavrilov@gmail.com> wrote:
>> On Thu, Jan 5, 2023 at 3:03 PM Christian König
>> <ckoenig.leichtzumerken@gmail.com> wrote:
>>> That one should be fixed by:
>>>
>>> commit 9f1ecfc5dcb47a7ca37be47b0eaca0f37f1ae93d
>>> Author: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>>> Date:   Wed Nov 23 03:13:03 2022 +0300
>>>
>> Christian,
>> This patch was written Nov. 23, 2022, but still not submitted in 6.2!
> It is in drm-misc-fixes and will be in 6.2 soon:
> https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-fixes&id=69555549cfa42e10f2fdd2699ed4e34d9d4f392b
>
>> Why?
> Patch review and end of year holidays.

And it looks like Dmitry submitted it initially to the wrong branch.

Because of this it wasn't scheduled as fix for 6.2, but rather queued up 
as new feature for 6.3.

This is fixed by now and the patch should show up in the next -rc.

Regards,
Christian.

>
> Alex
>
>> It will close my questions about amdgpu right now.
>>
>> Tested-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
>>
>> --
>> Best Regards,
>> Mike Gavrilov.


  reply	other threads:[~2023-01-06 15:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 10:47 [PATCH] drm/amdgpu: grab extra fence reference for drm_sched_job_add_dependency Christian König
2022-12-19 14:00 ` Borislav Petkov
2022-12-21 21:10   ` Alex Deucher
2023-01-03  8:34     ` Christian König
2023-01-03 14:26       ` Alex Deucher
2023-01-03 14:28         ` Michel Dänzer
2023-01-05  1:44         ` Mikhail Gavrilov
2023-01-05 10:03           ` Christian König
2023-01-06 12:59             ` Mikhail Gavrilov
2023-01-06 14:24               ` Alex Deucher
2023-01-06 15:27                 ` Christian König [this message]
2023-01-09 13:13                   ` Mikhail Gavrilov
2023-01-09 13:40                     ` Christian König
2023-01-10 18:21                       ` Mikhail Gavrilov
2023-01-12 12:05                         ` Christian König
2022-12-19 15:08 ` Luben Tuikov
2022-12-23 10:00 ` Michal Kubecek
2022-12-23 22:55 ` Mikhail Gavrilov

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=f4c965d9-d985-0030-7411-6d8d0f750058@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bp@alien8.de \
    --cc=michel@daenzer.net \
    --cc=mikhail.v.gavrilov@gmail.com \
    /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.