* Re: linux: update to 6.10.
2024-09-18 23:23 [PR PATCH] linux: update to 6.10 classabbyamp
@ 2024-09-18 23:44 ` abenson
2024-09-19 19:20 ` dkwo
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: abenson @ 2024-09-18 23:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 247 bytes --]
New comment by abenson on void-packages repository
https://github.com/void-linux/void-packages/pull/52268#issuecomment-2359634392
Comment:
Last I checked it was having crashes with 6.10, let me see if I can figure out if I already have the fix.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: linux: update to 6.10.
2024-09-18 23:23 [PR PATCH] linux: update to 6.10 classabbyamp
2024-09-18 23:44 ` abenson
@ 2024-09-19 19:20 ` dkwo
2024-09-19 19:20 ` dkwo
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: dkwo @ 2024-09-19 19:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 210 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/52268#issuecomment-2362004966
Comment:
Maybe at the same time bump mainline to 6.11, which seems to work fine?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: linux: update to 6.10.
2024-09-18 23:23 [PR PATCH] linux: update to 6.10 classabbyamp
2024-09-18 23:44 ` abenson
2024-09-19 19:20 ` dkwo
@ 2024-09-19 19:20 ` dkwo
2024-10-12 19:16 ` gc-user
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: dkwo @ 2024-09-19 19:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/52268#issuecomment-2362004966
Comment:
Maybe at the same time bump `linux-mainline` to 6.11, which seems to work fine?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: linux: update to 6.10.
2024-09-18 23:23 [PR PATCH] linux: update to 6.10 classabbyamp
` (2 preceding siblings ...)
2024-09-19 19:20 ` dkwo
@ 2024-10-12 19:16 ` gc-user
2024-10-12 19:18 ` gc-user
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: gc-user @ 2024-10-12 19:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/pull/52268#issuecomment-2408665967
Comment:
If zfs support is a deciding factor, why not wait for 6.12 and zfs to support it?
If my understanding and calculation is correct, it'll be the next LTS kernel.
Usually. when zfs comes out with a new version that supports a "current" kernel, that one falls out of support shortly after and zfs users can decide if they want to keep using an outdated kernel or downgrade to the newest LTS kernel.
But then "linux" would essentially become "linux-lts". On the other hand, there's also "linux-mainline". So, "the current thing" is already covered by that one... Anyway, the kernel between mainline and LTS is a short-lived kernel which doesn't really deserve it's own package (apart from the one with the version number in it, of course) IMHO - if the credo is. "don't use a kernel that is no longer supported".
But I might also be missing something and be totally wrong.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: linux: update to 6.10.
2024-09-18 23:23 [PR PATCH] linux: update to 6.10 classabbyamp
` (3 preceding siblings ...)
2024-10-12 19:16 ` gc-user
@ 2024-10-12 19:18 ` gc-user
2024-10-12 19:18 ` gc-user
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: gc-user @ 2024-10-12 19:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/pull/52268#issuecomment-2408665967
Comment:
If zfs support is a deciding factor, why not wait for 6.12 and zfs to support it?
If my understanding and calculation is correct, it'll be the next LTS kernel.
Usually. when zfs comes out with a new version that supports a "current" kernel, that one falls out of support shortly after and zfs users can decide if they want to keep using an outdated kernel or downgrade to the newest LTS kernel.
Maybe zfs will support 6.12 before 6.11 falls out of support, but that's probably not a sure bet.
But then "linux" would essentially become "linux-lts". On the other hand, there's also "linux-mainline". So, "the current thing" is already covered by that one... Anyway, the kernel between mainline and LTS is a short-lived kernel which doesn't really deserve it's own package (apart from the one with the version number in it, of course) IMHO - if the credo is. "don't use a kernel that is no longer supported".
But I might also be missing something and be totally wrong.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: linux: update to 6.10.
2024-09-18 23:23 [PR PATCH] linux: update to 6.10 classabbyamp
` (4 preceding siblings ...)
2024-10-12 19:18 ` gc-user
@ 2024-10-12 19:18 ` gc-user
2024-10-24 12:50 ` abenson
2024-11-14 19:32 ` [PR PATCH] [Closed]: " classabbyamp
7 siblings, 0 replies; 9+ messages in thread
From: gc-user @ 2024-10-12 19:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/pull/52268#issuecomment-2408665967
Comment:
If zfs support is a deciding factor, why not wait for 6.12 and zfs to support it?
If my understanding and calculation is correct, it'll be the next LTS kernel.
Usually. when zfs comes out with a new version that supports a "current" kernel, that one falls out of support shortly after and zfs users can decide if they want to keep using an outdated kernel or downgrade to the newest LTS kernel.
Maybe zfs will support 6.12 before 6.11 becomes EOL, but that's probably not a sure bet.
But then "linux" would essentially become "linux-lts". On the other hand, there's also "linux-mainline". So, "the current thing" is already covered by that one... Anyway, the kernel between mainline and LTS is a short-lived kernel which doesn't really deserve it's own package (apart from the one with the version number in it, of course) IMHO - if the credo is. "don't use a kernel that is no longer supported".
But I might also be missing something and be totally wrong.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: linux: update to 6.10.
2024-09-18 23:23 [PR PATCH] linux: update to 6.10 classabbyamp
` (5 preceding siblings ...)
2024-10-12 19:18 ` gc-user
@ 2024-10-24 12:50 ` abenson
2024-11-14 19:32 ` [PR PATCH] [Closed]: " classabbyamp
7 siblings, 0 replies; 9+ messages in thread
From: abenson @ 2024-10-24 12:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
New comment by abenson on void-packages repository
https://github.com/void-linux/void-packages/pull/52268#issuecomment-2435211104
Comment:
6.10 is now EOL.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PR PATCH] [Closed]: linux: update to 6.10.
2024-09-18 23:23 [PR PATCH] linux: update to 6.10 classabbyamp
` (6 preceding siblings ...)
2024-10-24 12:50 ` abenson
@ 2024-11-14 19:32 ` classabbyamp
7 siblings, 0 replies; 9+ messages in thread
From: classabbyamp @ 2024-11-14 19:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
There's a closed pull request on the void-packages repository
linux: update to 6.10.
https://github.com/void-linux/void-packages/pull/52268
Description:
zfs should support it, @abenson does nvidia support it?
^ permalink raw reply [flat|nested] 9+ messages in thread