Marc-Christian Petersen <m....@gmx.de> writes: > so, what's up with this fix? Any chance to get it into Debians kernel tree? > > It's kind of uncomfortable to rebuild the whole kernel, with this applied, > when Debian releases a new kernel which happens frequently ;->
I fully understand. I must admit that I thought it would be a no-brainer to verify this and get it into the upstream and the 2.6.32.x stable tree. But after nagging about it recently, it appears that the driver maintainer didn't really understand the issue. The last I heard from LSI was this: http://marc.info/?l=linux-scsi&m=129549117927641 which wouldn't be so bad if it weren't for the fact that it was sent well *after* that I already had done exactly that, as FUJITA Tomonori helpfully pointed out in a reply to that message.... So I honestly don't know. Looks like getting it upstream will still take some time. Maybe the Debian kernel maintainers can take it as a temporary bugfix until it gets there? The fix is rather obvious (in my eyes at least :-). Bjørn -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ei81pezs....@nemi.mork.no
