| Message ID | 20230921141516.520471-1-bigeasy@linutronix.de (mailing list archive) |
|---|---|
| Headers | show |
| Series | drm/amd/display: Remove migrate-disable and move memory allocation. | expand |
Am 21.09.23 um 16:15 schrieb Sebastian Andrzej Siewior: > Hi, > > I stumbled uppon the amdgpu driver via a bugzilla report. The actual fix > is #4 + #5 and the rest was made while looking at the code. Oh, yes please :) Rodrigo and I have been trying to sort those things out previously, but that's Sisyphean work. In general the DC team needs to judge, but of hand it looks good to me. Christian. > > Sebastian > >
On 2023-09-22 07:33:26 [+0200], Christian König wrote: > Am 21.09.23 um 16:15 schrieb Sebastian Andrzej Siewior: > > Hi, > > > > I stumbled uppon the amdgpu driver via a bugzilla report. The actual fix > > is #4 + #5 and the rest was made while looking at the code. > > Oh, yes please :) > > Rodrigo and I have been trying to sort those things out previously, but > that's Sisyphean work. > > In general the DC team needs to judge, but of hand it looks good to me. Any way to get this merged? There was no reply from the DC team… No reply from the person breaking it either. The bugzilla reporter stated that it solves his trouble. He didn't report anything new ;) > Christian. Sebastian
On 2023-10-02 06:58, Sebastian Andrzej Siewior wrote: > On 2023-09-22 07:33:26 [+0200], Christian König wrote: >> Am 21.09.23 um 16:15 schrieb Sebastian Andrzej Siewior: >>> Hi, >>> >>> I stumbled uppon the amdgpu driver via a bugzilla report. The actual fix >>> is #4 + #5 and the rest was made while looking at the code. >> >> Oh, yes please :) >> >> Rodrigo and I have been trying to sort those things out previously, but >> that's Sisyphean work. >> >> In general the DC team needs to judge, but of hand it looks good to me. > > Any way to get this merged? There was no reply from the DC team… No > reply from the person breaking it either. The bugzilla reporter stated > that it solves his trouble. He didn't report anything new ;) > Apologies for the slow progress. We're feeding it through our CI and will let you know the verdict soon. Do you happen to have the bugzilla link that this is fixing? It would be helpful to include that as a link in the patches as well, to give them context. Harry >> Christian. > > Sebastian
On 2023-10-03 15:54:58 [-0400], Harry Wentland wrote: > On 2023-10-02 06:58, Sebastian Andrzej Siewior wrote: > > On 2023-09-22 07:33:26 [+0200], Christian König wrote: > >> Am 21.09.23 um 16:15 schrieb Sebastian Andrzej Siewior: > >>> Hi, > >>> > >>> I stumbled uppon the amdgpu driver via a bugzilla report. The actual fix > >>> is #4 + #5 and the rest was made while looking at the code. > >> > >> Oh, yes please :) > >> > >> Rodrigo and I have been trying to sort those things out previously, but > >> that's Sisyphean work. > >> > >> In general the DC team needs to judge, but of hand it looks good to me. > > > > Any way to get this merged? There was no reply from the DC team… No > > reply from the person breaking it either. The bugzilla reporter stated > > that it solves his trouble. He didn't report anything new ;) > > > > Apologies for the slow progress. We're feeding it through our CI and > will let you know the verdict soon. > > Do you happen to have the bugzilla link that this is fixing? It would > be helpful to include that as a link in the patches as well, to give > them context. The bugzilla report is at https://bugzilla.kernel.org/show_bug.cgi?id=217928 but the patches explain the situation, too. Even more verbose than the report… > Harry Sebastian
On 2023-10-03 15:54, Harry Wentland wrote: > On 2023-10-02 06:58, Sebastian Andrzej Siewior wrote: >> On 2023-09-22 07:33:26 [+0200], Christian König wrote: >>> Am 21.09.23 um 16:15 schrieb Sebastian Andrzej Siewior: >>>> Hi, >>>> >>>> I stumbled uppon the amdgpu driver via a bugzilla report. The actual fix >>>> is #4 + #5 and the rest was made while looking at the code. >>> >>> Oh, yes please :) >>> >>> Rodrigo and I have been trying to sort those things out previously, but >>> that's Sisyphean work. >>> >>> In general the DC team needs to judge, but of hand it looks good to me. >> >> Any way to get this merged? There was no reply from the DC team… No >> reply from the person breaking it either. The bugzilla reporter stated >> that it solves his trouble. He didn't report anything new ;) >> > > Apologies for the slow progress. We're feeding it through our CI and > will let you know the verdict soon. > > Do you happen to have the bugzilla link that this is fixing? It would > be helpful to include that as a link in the patches as well, to give > them context. > CI passed. Series is Acked-by: Harry Wentland <harry.wentland@amd.com> Harry > Harry > >>> Christian. >> >> Sebastian >
On 9/21/23 08:15, Sebastian Andrzej Siewior wrote: > Hi, > > I stumbled uppon the amdgpu driver via a bugzilla report. The actual fix > is #4 + #5 and the rest was made while looking at the code. > > Sebastian > > Hi Sebastian, Thanks a lot for this patchset. We tested it on multiple devices, and everything looks good. I also reviewed it and lgtm. Reviewed-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> Thanks Siqueira
On 9/21/23 10:15, Sebastian Andrzej Siewior wrote: > Hi, > > I stumbled uppon the amdgpu driver via a bugzilla report. The actual fix > is #4 + #5 and the rest was made while looking at the code. > > Sebastian I have applied the series, thanks! > >
On 2023-10-04 08:44:58 [-0400], Harry Wentland wrote: > CI passed. > > Series is > Acked-by: Harry Wentland <harry.wentland@amd.com> Thank you. > Harry Sebastian