On Thu, Dec 04, 2025 at 08:31:29AM -0800, Barry K. Nathan wrote:
On 12/3/25 07:29, Greg Kroah-Hartman wrote:
6.12-stable review patch. If anyone has any objections, please let me know.
From: Philipp Hortmann philipp.g.hortmann@gmail.com
commit e8785404de06a69d89dcdd1e9a0b6ea42dc6d327 upstream.
As far as I can tell, this isn't the correct upstream commit. Commit e8785404de06a69d89dcdd1e9a0b6ea42dc6d327 upstream is "Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete" and I think the actual upstream commit for this patch is 41e883c137ebe6eec042658ef750cbb0529f6ca8.
Good catch! I'll go fix that up in all trees, thanks.
Once the incorrect upstream commit ID caught my attention, I also noticed the following:
The longterm kernels will still support this hardware for years.
The commit messages for the 5.15, 6.1, and 6.6 backports removed this line. (I'm mentioning this because I'm guessing the 6.12 backport commit message was also supposed to remove it.)
Find further discussions in the Link below.
Link: https://lore.kernel.org/linux-staging/a02e3e0b-8a9b-47d5-87cf-2c957a474daa@g... Signed-off-by: Philipp Hortmann philipp.g.hortmann@gmail.com Tested-by: Dominik Karol Piątkowski dominik.karol.piatkowski@protonmail.com Link: https://lore.kernel.org/r/20241020144933.10956-1-philipp.g.hortmann@gmail.co... Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org [groeck: Resolved conflicts] Signed-off-by: Guenter Roeck linux@roeck-us.net Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org
Another link that I believe does a better job of explaining why this driver is being removed from LTS kernels, and why now:
Link: https://lore.kernel.org/stable/20251204021604.GA843400@ax162/T/#t
Good point, I'll go make these changes, thanks!
greg k-h