Date: Sat, 27 Oct 2001 20:50:01 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: mjacob@feral.com Cc: Jonathan Lemon <jlemon@flugsvamp.com>, "Andrey A. Chernov" <ache@nagual.pp.ru>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_conf.c subr_disk.c Message-ID: <18358.1004208601@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 27 Oct 2001 11:36:43 PDT." <20011027113537.A67553-100000@wonky.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> The fact that the kernel has been whining about >> WARNING: driver mistake... >> all along wouldn't count as a HEADSUP would it ? >> >> It sure does to me... > >When you make a change that is likely to panic kernels for most people, it's a >courtesy to waste 30 seconds of email time. If the kernel prints odd messages containing words like "WARNING" "error", "mistake", "panic" and the name of your device driver or other reference to your code, you can safely ignore these messages as long as the system keeps running. It probably just means that you misunderstood some boring API or something, and you can rest assured that the committer working with that API will visit you personally (or call you on the phone inside business hours if you live more than 3 continents away) and explain to you what he will do to accomodate your use of the API. Should your kernel stop working because of such messages, you are free to abuse, threathen and use any kind of harrassment until somebody else fixes the problem in your code. -- "FreeBSD Kernel hacking for grief and loss" chapter 3, p. 4 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18358.1004208601>