On Thu, Jul 14, 2022 at 1:58 PM Andrey Grodzovsky <andrey.grodzovsky@xxxxxxx> wrote: > > On 2022-07-14 12:22, Alex Deucher wrote: > > > On Thu, Jul 14, 2022 at 10:14 AM Andrey Grodzovsky > > <andrey.grodzovsky@xxxxxxx> wrote: > >> > >> On 2022-07-14 05:57, Dmitry Osipenko wrote: > >>> On 7/12/22 11:56, Dmitry Osipenko wrote: > >>>> On 7/6/22 18:46, Alex Deucher wrote: > >>>>> On Wed, Jul 6, 2022 at 9:49 AM Andrey Grodzovsky > >>>>> <andrey.grodzovsky@xxxxxxx> wrote: > >>>>>> On 2022-07-06 03:07, Dmitry Osipenko wrote: > >>>>>> > >>>>>>> Hello Andrey, > >>>>>>> > >>>>>>> On 5/17/22 17:48, Dmitry Osipenko wrote: > >>>>>>>> On 5/17/22 17:13, Andrey Grodzovsky wrote: > >>>>>>>>> Done. > >>>>>>>>> > >>>>>>>>> Andrey > >>>>>>>> Awesome, thank you! > >>>>>>>> > >>>>>>> Given that this drm-scheduler issue needs to be fixed in the 5.19-RC and > >>>>>>> earlier, shouldn't it be in the drm-fixes and not in drm-next? > >>>>>> I pushed it into drm-misc from where it got into drm-next. I don't have > >>>>>> permission for drm-fixes. > >>>>> The -fixes branch of drm-misc. > >>>> Now I don't see the scheduler bugfix neither in the -fixes branch nor in > >>>> the -next and today Dave sent out 5.19-rc7 pull request without the > >>>> scheduler fix. Could anyone please check what is going on with the DRM > >>>> patches? Thanks! > >>>> > >>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffreedesktop%2Fdrm-misc%2Fcommits%2Fdrm-misc-fixes&data=05%7C01%7Candrey.grodzovsky%40amd.com%7Cd62c2e6d3ec748cd639608da65b52548%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637934125954377887%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WPmMC%2B%2Fy83cUctuF%2FLNo9VhWnB%2FkpUVQotMh74VshB8%3D&reserved=0 > >>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcgit.freedesktop.org%2Fdrm%2Fdrm-misc%2Flog%2F%3Fh%3Ddrm-misc-fixes&data=05%7C01%7Candrey.grodzovsky%40amd.com%7Cd62c2e6d3ec748cd639608da65b52548%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637934125954377887%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RzCMLUYLmUjSmvDm4E%2FJr%2B5rp7E8UvjFt1tmwBoBiVc%3D&reserved=0 > >>> The patch is in the drm-misc-next-fixes, so it wasn't moved to the > >>> drm-misc-fixes. > >>> > >>> Andrey, don't you have access to drm-misc-fixes? Or you meant > >>> drm-fixes=drm-misc-fixes? > >> > >> I have only accesses to drm-misc-next to which I pushed this patch. > > anyone with drm-misc rights can commit to any of the branches in the > > drm-misc tree. You just need to check out and push the appropriate > > branch. then push the changes. E.g., > > dim push-branch drm-misc-next > > vs > > dim push-branch drm-misc-next-fixes > > etc. > > > > Alex > > > I see, but what is the reason then that Dave sent out 5.19-rc7 pull > request without the > scheduler fix if the patch was merged into drm-misc-next long ago ? All > the changes from > there are usually picked up for pull requests, no ? drm-misc-next is for new stuff for the next kernel (e.g., 5.20). drm-misc-fixes is for fixes for the current kernel cycle (e.g., 5.19). See: https://drm.pages.freedesktop.org/maintainer-tools/drm-misc.html Alex > > Andrey > > > > > > > >> Andrey > >> > >>
