| 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: <20070129164330.GA4006@synertronixx3> Date: Mon, 29 Jan 2007 17:43:30 +0100 From: Konstantin Kletschke <lists@...gbr.de> To: linux-kernel@...r.kernel.org Cc: s.hauer@...gutronix.de, ppisa4lists@...ron.com Subject: Re: ARM i.MX serial: fix tx buffer overflows Am 2007-01-29 15:37 +0000 schrieb Russell King: > Is it really worth adding additional code to shut up this (imho) silly > warning? It's just adding needless complexity to drivers. As I pointed out in http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2006-November/037192.html the console gets flooded with this "warning" to unusable state sometimes. > What happens if a driver is used on multiple platforms, some of which > support trigger setting and others which don't? Are we going to end > up with a large #ifdef in every driver? I don't know exactly. But in addition to the fact, that this warning floods my console to unusable state I am used to sell software without warnings. If there are warnings my boss some things are broken. Konsti -- GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF - 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