Chris Hofstaedtler <z...@debian.org> writes: > * Diederik de Haas <didi.deb...@cknow.org> [221019 00:07]: >> On dinsdag 18 oktober 2022 23:44:17 CEST Chris Hofstaedtler wrote: >> > it appears quite some new btusb hardware was released recently. >> > linux-next has a lot of simple "Add xyz ID" patches for btusb.c: >> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/driv >> > ers/bluetooth/btusb.c >> > >> > Please consider applying 57117d7234dadfba2a83615b2a9369f6f2f9914f >> > and/or the other patches adding new hwids to btusb.c for the >> > bookworm kernel. >> >> It's already part of Linux 6.1-rc1 and it is expected that 6.1 will be the >> next LTS release and I'd guess thus also the Bookworm kernel. >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/drivers/bluetooth?h=v6.1-rc1 > > Right, that'd be good. I've manually applied > 57117d7234dadfba2a83615b2a9369f6f2f9914f against 5.9.11-1, and that > works for me; but only after making available > BT_RAM_CODE_MT7922_1_1_hdr.bin from linux-firmware.git.
If this is a simple device ID addition without any other dependencies, then it qualifies for Linux stable. And you'll get it in Debian stable for free. New device ID patches are regularily backported to the maintained stable kernels, and usually picked up automatically by the stable maintainers. You can request a backport of a specific commit in mainline by sending an email to sta...@vger.kernel.org See https://docs.kernel.org/process/stable-kernel-rules.html Bjørn
