whoever the maintainer of the -stable/-longterm tree is (be it anSo i have to contact Greg Kohan from SUSE directly?
individual or a team employeed by some comapny) then looks at the patch
and considers backporting it (if it's too hard, or to intrusive, they
may decide not to).
the idea of the lonterm kernels is that organizations need to maintain aThat was what i thoght. So a bug like this should get fixed right? Otherwise this makes no sense. Sadly Redhat has ported the fix back in his RHEL 6 2.6.32 kernel but they haven't send the patch to stable / vanilla team.
kernel for a long time due to commitments that they have made (Debian
doesn't want to change the kernel it ships in a stable version, RedHat
doesn't want to change the kernel version in a RHEL release, etc), and
so they publicly announce this so that anyone else wanting to use the
same kernel version can share in the work (and therefor everyone can
benifit from each other's work)