Private driver support emails should be avoided.

[Jeff Garzik <jeff@garzik.org>]

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

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

Unless there is a security issue (email security@kernel.org), posters 
should ALWAYS email their report(s) to one or more mailing lists.

Private email
* is not archived publicly
* is not Google-able
* restricts the sharing of knowledge
* prevents other users from responding to your email

Feel free to CC me on problems you think should warrant my attention.  A 
carbon copy is acceptable to almost all regular kernel contributors.


As another tip, if a kernel bug or annoyance persists, people are 
encouraged to maintain wiki and web pages describing the behavior, and 
discussed problem history.  Maintaining "SATA sucks on ThinkPad" style 
web pages is always a good way to shame kernel hackers into action ;-) 
Maintaining such web pages is a good way for a group of affected users 
to pool common information, and suggested workarounds.

Ensuring the freshness of bugzilla.kernel.org information is also a 
great way for non-kernel hackers to help out.  Sometimes a bug is only 
solved after a pattern emerges from a group of problem reports.  Even 
"me too!" bugzilla reports are helpful...  if they are followed by 
highly detailed hardware and kernel information.

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/