| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTin0GuV28NsXwK6Pzo3cZ24Jn3WLR2YL9L660Us_@mail.gmail.com> Date: Tue, 25 May 2010 07:51:45 +0530 From: Satish Eerpini <eerpini@...il.com> To: linux-kernel <linux-kernel@...r.kernel.org>, linux-wireless@...r.kernel.org Subject: iwl3945 bug in 2.6.34 > Actually, sorry, but that patch will not work on 2.6.34 since the > feature it enables is not present there - it will be in 2.6.35 though. > To enable the feature in 2.6.34 will take some more backporting effort > that I'm looking into now. > the patch does lead to a reject, I am not very experienced with code-fu in the kernel, and have no clue about the iwl code base, but comparing the code from 2.6.24 and the latest compat-wireless tarball, I found that in iwl-core.c iwl_check_stuck_queue iwl_bg_monitor_recover are not present in the 2.6.34 version of the file, is there a particular reason for doing this ? is there a patch series/discussion I can follow to know the details on this ? and I am trying to compile 2.6.34 by adding just these two functions to iwl-core.c. If that works I will report back (though you might already know if it will work or not) Cheers Satish -- http://tuxitter.blogspot.com -- http://tuxitter.blogspot.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists