Hi Ralf, On Fri, Jan 04, 2019 at 11:42:26AM +0100, Ralf Jung wrote: > Hi, > > > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: > >> Package: linux-image-4.18.0-0.bpo.3-amd64 > >> Version: 4.18.20-2~bpo9+1 > >> Severity: normal > >> Tags: upstream > >> > >> Dear Maintainer, > >> > >> I reported an upstream bug at > >> <https://marc.info/?l=linux-netdev&m=154635529809577&w=2> that got a patch > >> submitted with <https://marc.info/?l=linux-netdev&m=154648423826010&w=2>. > >> It would be great to have this patch applied to the next Debian kernel > >> update. > > > > Queued it up for our next sid upload, as per > > https://salsa.debian.org/kernel-team/linux/commit/c91e16558f8fe6f1fa4df2faa27ad69afa397d03 > > Thanks a lot! > > How are updates to the stable-backports kernel usually handled?
Once a version uploaded to sid, migrates to testing, it can be prepared for stable-backports based on that. So what will need to happen here: upload of 4.19.13-2 to unstable (actually possibly only >= 4.19.14-1 if we do not have pressure to upload 4.19.13-2), then wait it migrates to testing, then the stretch-backports upload can be done. Hope this helps, Regards, Salvatore
