linux-kernel - Re: Private driver support emails should be avoided.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	04 Aug 2006 10:46:03 -0400
From:	Jes Sorensen <jes@....com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Netdev List <netdev@...r.kernel.org>
Subject: Re: Private driver support emails should be avoided.

>>>>> "Jeff" == Jeff Garzik <jeff@...zik.org> writes:

Jeff> Just a reminder to folks out there...  Don't send private driver
Jeff> support emails.

Jeff> I receive a lot of email.  A lot.  Not as much as Linus or
Jeff> Andrew probably, but still sizable.  And quite regularly, I will
Jeff> receive a private email asking for help on a SATA or net driver
Jeff> problem.  The poster will include various details on their
Jeff> problem, and ask for help debugging the problem.  While the
Jeff> email will indeed be skimmed -- looking at a mass of bug
Jeff> reports, one can better detect patterns -- the people seeking
Jeff> support privately will almost NEVER RECEIVE A RESPONSE.

Jeff,

Very sane - I get some of it too, though less so these days :)

What about writing this up and sticking it under
Documentation/Reporting-Bugs or something so there's an easy reference
to it?

Cheers,
Jes
-
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/