| 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
| ||
|
Date: Sun, 21 Sep 2008 16:48:29 -0700 (PDT) From: David Miller <davem@...emloft.net> To: johnpol@....mipt.ru Cc: alan@...rguk.ukuu.org.uk, arjan@...radead.org, johannes@...solutions.net, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, ipw2100-devel@...ts.sourceforge.net, linux-wireless@...r.kernel.org, yi.zhu@...el.com, reinette.chatre@...el.com, jgarzik@...ox.com, linville@...driver.com Subject: Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart. Evgeniy, you're bordering on being an asshole, if not actually being one. If you behaved this way for a bug I was responsible for, I would absolutely ignore you until you settled down and started to behave more reasonably. You're acting like a bomb which is about to explode, which is probably why the actual Intel maintainers for this driver don't want to touch you with a ten foot pole. You're being volatile and extremely unpleasant to interact with about this issue. The Intel folks replying to you right now are general Intel linux folks who are trying to help you, not the driver maintainers who can look into the firmware and attack that angle. So give them A FUCKING BREAK! Getting the OOPS to kerneloops.org is the way forward and will help your cause, whether you believe it or not. -- 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