On Thu, 2010-05-20 at 07:24 +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > For Omsa 6.0.1 is need mptlinux version more than 3.04 present in kernel > I have download 4.22 from lsi site and try build update driver with dkms, i > have already do same on 2.6.26 past without problem but with 2.6.32 give this > compilation error: > > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c: In function > ‘mptsas_smp_handler’: > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2757: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2758: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2775: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2805: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2808: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2821: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2823: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2854: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2855: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2864: error: ‘struct request’ > has no member named ‘data_len’ > /var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.c:2867: error: ‘struct request’ > has no member named ‘data_len’ > make[3]: *** [/var/lib/dkms/mptlinux/4.22.00.00/build/mptsas.o] Error 1 > make[2]: *** [_module_/var/lib/dkms/mptlinux/4.22.00.00/build] Error 2 > make[1]: *** [sub-make] Error 2 > make: *** [all] Error 2 > > Is possible update mptlinux on new kernel version please? bugzilla.kernel.org is for actual bugs within the linux kernel, not for problems with out of tree drivers. The issue you're trying to report needs to be fixed by LSI. While it's not impossible they would notice this request on the scsi mailing list, you're much more likely to get their attention by requesting support directly from them. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
