Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #76327 > unrolled thread

Bug#989705: closing 989705

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#989705: closing 989705 Computer Enthusiastic <computer.enthusiastic@gmail.com> - 2022-09-20 11:40 +0200
    Bug#989705: closing 989705 Salvatore Bonaccorso <carnil@debian.org> - 2022-09-20 12:40 +0200
      Bug#989705: closing 989705 Salvatore Bonaccorso <carnil@debian.org> - 2022-10-04 21:10 +0200
      Bug#989705: closing 989705 Computer Enthusiastic <computer.enthusiastic@gmail.com> - 2022-10-04 21:30 +0200
        Bug#989705: closing 989705 Computer Enthusiastic <computer.enthusiastic@gmail.com> - 2023-02-05 18:30 +0100
          Bug#989705: closing 989705 Salvatore Bonaccorso <carnil@debian.org> - 2023-02-05 21:00 +0100

#76327 — Bug#989705: closing 989705

Hello,

Il giorno mar 20 set 2022 alle ore 09:33 Salvatore Bonaccorso
<carnil@debian.org> ha scritto:
>
> close 989705 5.19.6-1
> thanks

What could be done to make the patch land in the current Debian Stable
(Bullseye) kernel release ?

Thanks.

[toc] | [next] | [standalone]

#76328

Hi,

On Tue, Sep 20, 2022 at 11:37:34AM +0200, Computer Enthusiastic wrote:
> Hello,
> 
> Il giorno mar 20 set 2022 alle ore 09:33 Salvatore Bonaccorso
> <carnil@debian.org> ha scritto:
> >
> > close 989705 5.19.6-1
> > thanks
> 
> What could be done to make the patch land in the current Debian Stable
> (Bullseye) kernel release ?

It should land in the 5.10.y stable series which we will then pick up
automatically on next rebases. But what is puzzling is that the commit
has been marked for stable only v5.15+. If you were able to confirm it
is actually present in 5.10.y as well then it needs a followup to be
picked as well for the 5.10.y stable series.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#76429

Hi,

On Tue, Oct 04, 2022 at 07:39:23PM +0200, Computer Enthusiastic wrote:
> Hello Salvatore,
> 
> Il giorno mar 20 set 2022 alle ore 12:32 Salvatore Bonaccorso
> <carnil@debian.org> ha scritto:
> >
> > Hi,
> [..]
> > >
> > > What could be done to make the patch land in the current Debian Stable
> > > (Bullseye) kernel release ?
> >
> > It should land in the 5.10.y stable series which we will then pick up
> > automatically on next rebases. But what is puzzling is that the commit
> > has been marked for stable only v5.15+. If you were able to confirm it
> > is actually present in 5.10.y as well then it needs a followup to be
> > picked as well for the 5.10.y stable series.
> >
> > Regards,
> > Salvatore
> 
> Yes, the patch is marked as only v5.15+, but the issue is still there
> in kernel 5.10, too.
> 
> As you suggested, I have tested the vanilla kernel 5.10.145 with and
> without kernel patches, as reported here [0].

Seen that, and thanks for having taken the time to test the case with
and without patch with newest 5.10.y version. This will hopefully help
to get the patch applied to 5.10.y as well so we can pick it up.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#76430

Hello Salvatore,

Il giorno mar 20 set 2022 alle ore 12:32 Salvatore Bonaccorso
<carnil@debian.org> ha scritto:
>
> Hi,
[..]
> >
> > What could be done to make the patch land in the current Debian Stable
> > (Bullseye) kernel release ?
>
> It should land in the 5.10.y stable series which we will then pick up
> automatically on next rebases. But what is puzzling is that the commit
> has been marked for stable only v5.15+. If you were able to confirm it
> is actually present in 5.10.y as well then it needs a followup to be
> picked as well for the 5.10.y stable series.
>
> Regards,
> Salvatore

Yes, the patch is marked as only v5.15+, but the issue is still there
in kernel 5.10, too.

As you suggested, I have tested the vanilla kernel 5.10.145 with and
without kernel patches, as reported here [0].

Thanks.

[0] https://lists.freedesktop.org/archives/nouveau/2022-September/041182.html

[toc] | [prev] | [next] | [standalone]

#78199

Hello Salvatore,

On Tue, 4 Oct 2022 19:39:23 +0200 Computer Enthusiastic 
<computer.enthusiastic@gmail.com> wrote:
> Hello Salvatore,
> 
> Il giorno mar 20 set 2022 alle ore 12:32 Salvatore Bonaccorso
> <carnil@debian.org> ha scritto:
> >
> > Hi,
> [..]
> > >
> > > What could be done to make the patch land in the current Debian Stable
> > > (Bullseye) kernel release ?
> >
> > It should land in the 5.10.y stable series which we will then pick up
> > automatically on next rebases. But what is puzzling is that the commit
> > has been marked for stable only v5.15+. If you were able to confirm it
> > is actually present in 5.10.y as well then it needs a followup to be
> > picked as well for the 5.10.y stable series.
> >
> > Regards,
> > Salvatore
> 
> Yes, the patch is marked as only v5.15+, but the issue is still there
> in kernel 5.10, too.
> 
> As you suggested, I have tested the vanilla kernel 5.10.145 with and
> without kernel patches, as reported here [0].
> 
> Thanks.
> 
> [0] https://lists.freedesktop.org/archives/nouveau/2022-September/041182.html

Thank you for supporting me to explain upstream the request for 
backporting the patch to 5.10.y.

The patch has been backported to Linux 5.10.166 few days ago [1].

I suppose it will hopefully be available in the Linux kernel shipped 
with the next Debian point release.

---
[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=v5.10.166

[toc] | [prev] | [next] | [standalone]

#78201

Hi,

On Sun, Feb 05, 2023 at 06:20:54PM +0100, Computer Enthusiastic wrote:
> Hello Salvatore,
> 
> On Tue, 4 Oct 2022 19:39:23 +0200 Computer Enthusiastic
> <computer.enthusiastic@gmail.com> wrote:
> > Hello Salvatore,
> > 
> > Il giorno mar 20 set 2022 alle ore 12:32 Salvatore Bonaccorso
> > <carnil@debian.org> ha scritto:
> > >
> > > Hi,
> > [..]
> > > >
> > > > What could be done to make the patch land in the current Debian Stable
> > > > (Bullseye) kernel release ?
> > >
> > > It should land in the 5.10.y stable series which we will then pick up
> > > automatically on next rebases. But what is puzzling is that the commit
> > > has been marked for stable only v5.15+. If you were able to confirm it
> > > is actually present in 5.10.y as well then it needs a followup to be
> > > picked as well for the 5.10.y stable series.
> > >
> > > Regards,
> > > Salvatore
> > 
> > Yes, the patch is marked as only v5.15+, but the issue is still there
> > in kernel 5.10, too.
> > 
> > As you suggested, I have tested the vanilla kernel 5.10.145 with and
> > without kernel patches, as reported here [0].
> > 
> > Thanks.
> > 
> > [0] https://lists.freedesktop.org/archives/nouveau/2022-September/041182.html
> 
> Thank you for supporting me to explain upstream the request for backporting
> the patch to 5.10.y.
> 
> The patch has been backported to Linux 5.10.166 few days ago [1].
> 
> I suppose it will hopefully be available in the Linux kernel shipped with
> the next Debian point release.

Yes I'm aware. It will be in the update which rebases to at least to
5.10.166 and is currently pending at
https://salsa.debian.org/kernel-team/linux/-/merge_requests/644 .

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web