[Bug 276985] crash in LinuxKPI/drm
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 276985] Crash in scheduler __curthread"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 03 Sep 2024 11:56:17 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #33 from feh@fehcom.de --- Hi, > My last question - if you are the drm module maintainer / developer - would it be > possible to mark following ports with incremental numbers like 510, 515, 610, not 61 > for a newest release please (61 < 515)? AFAIK those numbers come from the Linux development. The AMD people build their drivers here and those numbers are related to the Kernel version: 5.15 => Linux Kernel 5.15 6.1 => Linux Kernel 6.1 (6.10 is current) It would not be a good idea to setup a new/different nameing scheme. As a developer/maintainer/porter I would rather stay close to upstream. --eh. PS: Linus doesn't follow Semantic Versioning strictly, thus there is no real breaking difference between the 5.x and 6.y branch. This may change with Rust in the kernel, but this is a different story. PPS: So far, the new DRM seems to work well. -- You are receiving this mail because: You are the assignee for the bug.